Chromium throttles WebTransport connections causing connection instability

[oblique]

At some point Chromium starts printing the following warnins in console:

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

This is due to a throttling algorithm that Chromium applies to WebTransport. When this happen, we can not establish any new WebTransport connections and we have the following effects:

1. On average we have only 5 peers connected with our node (In Firefox we have ~60 peers connected).
2. After some time we might reach to 0 peers and syncing will stop until new connection are allowed by Chromium.

js-lip2p team reported this to Chromium and they didn't manage to workaround it. However they are close to submitting a patch in Chromium that will apply throttling per-host basis (tracking issue: libp2p/js-libp2p#1896).

This is a blocker issue because it affects the stability of our node.