Tracking issue: Finish WebTransport Support

[marten-seemann]

eta: 2023Q1

We shipped experimental WebTransport support in v0.23.0. There are a few things we still need to do to completely finish the project.

• archive https://github.com/marten-seemann/go-libp2p-webtransport/
• docs entry for WebTransport: Add content for WebTransport docs#198
• get the WebTransport spec merged: add a WebTransport spec specs#404
• webtransport: use the resource manager to control flow control window increases #1826
• webtransport: deterministically generate certificates, to survive host reboots #1824
• webtransport: enable qlogging (via QLOGDIR) #1825
• webtransport / quic: allow listening on the same UDP port #1759

Once js-libp2p has released WebTransport support:

• write an announcement to shipped@ mailing list
• write a blog post: add a WebTransport blog post blog#11

And then, assuming that our experiment (see https://github.com/protocol/bifrost-infra/issues/2114) is successful:

• add WebTransport to the list of default transports #1915

[BigLep]

This is great - thanks @marten-seemann !

optional: write a blog post

I would remove optional. We've got to to do this. We have a lot of "tree shaking" to do here to make sure folks are awareof what is possible!

[p-shahi]

https://github.com/ipfs/kubo/releases/tag/v0.18.0 is out, I think we can do the shipped email now @marten-seemann