Deluge of protocol rejections

I'm not entirely sure if this is due to our usage or something else, but any pointers would also be welcome.
Our server launches beetswap and gets a deluge of rejected protocol selections:

```
2025-03-17T17:47:22.006243Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: yamux::connection: f9d81456: new outbound (Stream f9d81456/13) of (Connection f9d81456 Client (streams 0))
2025-03-17T17:47:22.006250Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Proposed protocol: /ipfs/bitswap/1.2.0
2025-03-17T17:47:22.006346Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Received rejection of protocol: /ipfs/bitswap/1.2.0
2025-03-17T17:47:22.006360Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: yamux::connection: f9d81456: new outbound (Stream f9d81456/15) of (Connection f9d81456 Client (streams 0))
2025-03-17T17:47:22.006365Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Proposed protocol: /ipfs/bitswap/1.2.0
2025-03-17T17:47:22.006467Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Received rejection of protocol: /ipfs/bitswap/1.2.0
2025-03-17T17:47:22.006485Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: yamux::connection: f9d81456: new outbound (Stream f9d81456/17) of (Connection f9d81456 Client (streams 0))
2025-03-17T17:47:22.006492Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Proposed protocol: /ipfs/bitswap/1.2.0
2025-03-17T17:47:22.006594Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Received rejection of protocol: /ipfs/bitswap/1.2.0
2025-03-17T17:47:22.006608Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: yamux::connection: f9d81456: new outbound (Stream f9d81456/19) of (Connection f9d81456 Client (streams 0))
2025-03-17T17:47:22.006614Z DEBUG new_established_connection{remote_addr=/ip4/127.0.0.1/tcp/62649 id=1 peer=12D3KooWAHtvsKEUJruwdGsSbFFR9eTkMP4JoFru3f19uJPEp3sf}:Connection::poll: multistream_select::dialer_select: Dialer: Proposed protocol: /ipfs/bitswap/1.2.0
```

This goes on for a while.

When this happens, there are multiple libp2p nodes in the network but only 1 (the one producing these logs) supports bitswap

Begin with the reported beetswap startup logs and the repeated /ipfs/bitswap/1.2.0 protocol rejections. Compare this behavior with the fact that only one network node supports bitswap, then trace the relevant libp2p connection and protocol-selection entry points. Done means determining whether the rejections are expected or identifying why the attempts repeat and documenting or fixing that behavior.

Written by the indexing model from the issue text.