Experiment: Hamachi-like built in setup

[jacobtread]

Description

Due to there being a fairly decent chance that QoS servers aren't going to be viable going forward as progress with them has been fairly stagnant it might be a far better solution to instead use a "Hamachi"-like setup for virtually routing traffic between clients through the server

Checklist

• [ ] Client can setup the virtual network and forward any messages through the server
• [ ] Server can handle mappings between virtual addresses and the actual clients
• [ ] Server can route messages through itself to the correct targets

[jacobtread]

Edit: Might actually be beneficial to instead create a "Relay" server that's separate from the main server that is in charge of only virtual address mapping and forwarding which would allow it to be isolated (Maybe allowing multiple people to share a "relay" server), and making it an option in the client to use a specific relay server that way those with stricter internet can go through a relay server and those without can use standard connections (open network?)

[jacobtread]

From Discord: Sadly looks like this tunneling approach isn't going to work out, likely its going to end up too clunky with all the libraries and dependencies ill need to pull. It might be more desirable to instead stick to third party solutions for virtual LAN networks using the new "hamachi" configuration I've added to the server for v0.5.11 (can rename this later since its not really hamachi specific). For now I will continue working on the QoS server approach to see if I can get that working properly instead

Closing this issue and will re-open it if I decide to re-visit this approach