Using a different QUIC implementation

I know that quic-go is the preferred solution here as they both share the same language. But I feel like that it would be a good idea to open up this application for allowing other QUIC implementations in its roots. e.g. we could then toy around with MsQuic which already supports connection migration or be able to switch over to a different stack that might become the reference implementation in the future.

i'm not fully sure how feasible that is but I just wanted to throw that idea into the pool and maybe get some feedback on it ^^

The issue does not name files, tests, or entry points. Start by locating where ssh3 integrates quic-go, then assess how an alternative QUIC implementation such as MsQuic could be selected and whether the existing interfaces support it. Done would require an agreed design and a working implementation with coverage for the supported QUIC backends.

Written by the indexing model from the issue text.