fix: do not add abort signals to "useless" addresses

[vasco-santos]

Node warns of a possible memory leak thanks o added event listeners on abortSignal:

(node:52434) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit
at EventTarget.[kNewListener] (node:internal/event_target:256:17)
at EventTarget.addEventListener (node:internal/event_target:335:23)
at anySignal (node_modules/any-signal/index.js:27:12)
at node_modules/libp2p/src/dialer/dial-request.js:70:85
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:94:5)

This started to happen when we start supporting dnsaddr resolution and js-ipfs started using bootstrap nodes with such addresses. Once these dnsaddr records are resolved, we get a large list of multiaddrs for the given peer, where several addresses are not relevant for JS libp2p dialer as we do not support transports for them (quic).

Despite having several useless addresses, during the dial flow we only checked if we have any transport to dial a peer on the transport-manager layer, which essentially means we are adding unnecessary event listeneres and creating unnecessary promises to be resolved for each of the addresses that will simply be rejected further on the stack.

This PR fixes the above issue by simply filtering out in the beginning of the dial flow the addresses that will not be useful.

Closes #900

[Gozala]

Looks good to me