bug: WebTransport session establishment failed. Too many pending WebTransport sessions (64)

[SgtPooki]

Sometimes I see thousands instances of this warning in Chrome:

WebTransport session establishment failed. Too many pending WebTransport sessions (64)

This module may need some sort of dial queue to ensure it doesn't open too many connections and trigger this error.

ported over from libp2p/js-libp2p-webtransport#64

[SgtPooki]

I believe this is a blocker for ipfs/helia#182 because:

1. webtransport is one of the few consistent ways we can connect to other nodes from the browser.
2. A Helia nodes' connectivity become unstable once we have too many pending dials.

@maschad are you actively working on this?

[maschad]

I'm not actively working on it at the moment @SgtPooki although I think @achingbrain 's PR #1947 may be related.

[achingbrain]

I think #1947 will help with the unstable bit but I can't help but wonder if there's some cleanup we need to do that we're missing to prevent the "Too many pending sessions" thing in the first place.