[Bug] Out-of-range port does not generate an error

[O1LER]

Fill out general information OS (windows, linux, ...): Windows 10 BeamMP-Server Version: 3.1.1

Describe the bug You can set a port in the serverConfig.toml that is above the allowed IPv4 portrange of 65535. The server binary will happily accept that port without an error, but of course theres no way to connect to that port

To Reproduce Steps to reproduce the behavior:

1. Enter a port number higher than 65535 in the serverConfig.toml
2. Start the server binary
3. It will report that the server is successfully running on the chosen port
4. But theres no way to connect to that port

Expected behavior A .toml file will accept any input of course, but at least the server binary should throw an error when the port is out-of-range Adding to that, too low of a port (<1024) should also throw an error.

Additional context