netcode.io connect tokens fail when letting the system assign a server port.

[maxweisel]

Steps to reproduce:

1. Set log level to DEBUG
2. Create a netcode server, initialize with a valid IP, but a port of 0 (system should assign)
3. Ask the netcode server to generate a connect token.
4. Use the connect token to connect to the server.
5. netcode server binds to a port correctly, and even generates connect tokens that include the assigned port. However, netcode server logs: server ignored connection request. server address not in connect token whitelist

I found this log in netcode here:
https://github.com/networkprotocol/netcode.io/blob/master/netcode.c#L4245

If I add a log to netcode_address_equal that uses netcode_address_to_string to print the addresses, I get something like this:

netcode_address_equal: '1.2.3.4' '1.2.3.4:49315'

Essentially, the connect token sent to the client includes the port assigned to the server by the system, however, server->address still references the netcode_address without the port assignment.

I'm happy to make a patch, but I don't understand how the connect token is getting an address with the valid port, but server->address doesn't include it.

Max