fix(quic): add support for reusing an existing socket for local dialing

[arsenron]

Description

Tracked in #4259. Now if a listener supports loopback interfaces, when a remote address is also a loopback address, we reuse an existing listener.

Notes & open questions

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• A changelog entry has been made in the appropriate crates

[mxinden]

Neat! Thank you @arsenron for the work.

Would you mind adding a unit test as well? This should be relatively straight forward. Given two nodes A and B:

1. Have A listen on 0.0.0.0:0.
2. Given the wildcard port (:0) store the concrete port chosen by the OS across all interfaces.
3. Have B listen on 127.0.0.1:0.
4. Have A dial B.
5. Expect the source port of A at B to be the port stored in (2), i.e. to be A's listen port.

[mergify]

This pull request has merge conflicts. Could you please resolve them @arsenron? 🙏

[arsenron]

Neat! Thank you @arsenron for the work.

Would you mind adding a unit test as well? This should be relatively straight forward. Given two nodes A and B:

1. Have A listen on `0.0.0.0:0`.

2. Given the wildcard port (`:0`) store the concrete port chosen by the OS across all interfaces.

3. Have B listen on `127.0.0.1:0`.

4. Have A dial B.

5. Expect the source port of A at B to be the port stored in (2), i.e. to be A's listen port.

Done.

[mxinden]

Wow, that was fast. Thank you! Two suggestions.

[mxinden]

Thank you for adjusting the test.

[arsenron]

@mxinden Rewrote using a HashSet instead of a bool to make the logic more reliable

[mxinden]

Well done @arsenron! Thank you for the help.

[mxinden]

Tagged and published.