This updates StunClient-related commands to be more IPV6-compatible, when the time will come to change.
There are 2 technical hurdles:
- the STUN server itself must be IPV6-accessible, and return IPV6 addresses (I think the latter will be automatic if/once we have the former).
- Enet must use IPV6-compatible sockets, which it does not (see #4301).
Beyond that, this code changes makes it so that the Networking:: namespace is protocol-independent, so it would be a matter of changing both 'ResolveIp' calls in StunClient to not force IPV4, and switch the connection data parsing to use IPV6.
This also moves a bit of code and cleans up some confusing (imo) logic flow.