Done criteria

1. libp2p's WebTransport transport is enabled by default.
2. There are corresponding docs that describe how/why to use this.

Background

With #9289 Kubo added opt-in webtransport support. This is covered more in the spec, but WebTransport provides a performant way for browsers (Chromium currently) to connect with the rest of the libp2p network. We want to enable browser nodes to be able to communicate easily with other nodes in the network. To accomplish this we need a good amount of nodes in the network to have webtransport listen addresses. Getting Kubo nodes having WebTransport listening by default is a good way to increase the number of nodes that browser nodes can connect to.

Preconditions

1. go-libp2p WebTransport transport has shown to be stable. This will come from WebTransport being used in the wild, including enabling it on some of PL's infra per https://github.com/protocol/bifrost-infra/issues/2114 . (Additional tracking of go-libp2p's WebTransport work is in [Tracking Issue] Experimental WebTransport Transport libp2p/go-libp2p#1717 or will be linked from there.)
2. webtransprot and quic can listed on the same port in go-libp2p: webtransport / quic: allow listening on the same UDP port libp2p/go-libp2p#1759
   • go-libp2p v0.24 libp2p/go-libp2p#1766
   • migrations needed after updating go-libp2p v0.24.0 update #9410

Notes about the work involved

1. This does involve a config migration
2. Documenting the browser/Kubo communication story is covered Document how to connect browser nodes with Kubo nodes using WebTransport ipfs-docs#1286