feat: add support for web transports

[sruehl]

resolves #190
resolves #193

[philippseith]

Nice!
Were you able to verify it with any third party client/server? AFAIK aspnetcore did not implement it yet: dotnet/aspnetcore#39583

[sruehl]

At the moment I'm in the process of verification, hence the PR is still in draft. I'll update here once I know that it works

[sruehl]

This way the way I noticed btw as this lead to a nasty nil pointer at a completely unrelated place (connection nil and error nil at the same time).

[sruehl]

Also I wonder if we should merge it in this state and fix potential issues later or temporary return a proper error on master?

[sruehl]

And regarding the failing Unit test. I have no idea what is going on there...

[sruehl]

Also I wonder if we should merge it in this state and fix potential issues later or temporary return a proper error on master?

@philippseith I prepared a PR for option 2 #192.

[sruehl]

seems that Unit test failure is unrelated to this PR and is caused by 35b4977

[sruehl]

I rebased this on #192

[sruehl]

This PR should no be safe to merge as it fixes two issues:

1. When Server responds WebTransports the client should stop panic (fix: don't panic when encountering web transports #192 at least stops the panic but you still get a error when Server responds with this Transport type)
2. WebTransports is only used in this state when the Client explicitly configures the Transport via ClientOptions