Use QUIC as transport protocol

QUIC is a UDP based protocol that offer rialable transportation of data. HTTP3 uses it.

An advantage is that it uses connection ID's over IP adresses plus port number to indentify a connection. I.e. when a user switches from a mobile connection to Wifi, or switches Wifi access points - the stream can continue where it left off - following a different path.

Feature request:

• Consider running game protocol over QUIC.
• Or, consider adding a connection ID to the protocol. Allowing user within i.e. the time frame of 60 seconds to reconnect to a running game - using a new tcp/ip connection.

Benefit:

• Multi player games can continue after the TCP connection of one client drops.
• People have an oppertunity to switch from Wifi to Cable - in gane.
• With a force reconnexct button under settings. Players can do a quick reconnect - where a new TCP connection may have less lag.

The issue names no files, tests, or entry points. Start by locating OpenRA's current TCP game-connection handling and documenting how transport changes or reconnects would fit it. Done would require a decided approach—QUIC transport or connection-ID-based reconnection—with successful continuation after a client network change.