feat: auto-dialer max queue should allow specifying max queue per transport

[SgtPooki]

https://github.com/libp2p/js-libp2p/blob/7debe0312f6df68e27dc26410a745c98477abe59/packages/libp2p/src/connection-manager/auto-dial.ts#L122C32-L122C54

WebTransport currently only supports 64 instances: #1896

Others may have their own limits (or none) and users should be able to limit autoDialMaxQueueLength by transport.

[SgtPooki]

related to #744 (comment)

[maschad]

Others may have their own limits (or none) and users should be able to limit autoDialMaxQueueLength by transport.

Given that it turns out this is actually an issue in chrome as discussed here this may not be the best solution since the dials are actually not pending (and thus shouldn't be in the dial queue at that point)

That being said this may be a good thing to have in the future.

[achingbrain]

Closing as the problem this proposal attempts to solve actually seems to be a bug in Chrome around WebTransport sessions never leaving the pending state.

This feature may be worth investigating in the future if a requirement surfaces but right now it's not something we need.