Elliot.

@dangell7 - do you have an opinion on whether this should be considered for the next release (2.0.0) or if it's ok for it to wait for 2024? (The first...

- bug fix. Should not require perf signoff. cc @sophiax851

@dangell7 1. This PR has conflicts that must be resolved. 2. After resolving, please confirm that you still think this PR is ready to merge.

@ximinez is this PR worth merging as-is? If not, let's close it, and you can open a new PR with your preferred changes.

Additionally/ideally, there would be no crosstalk between networks. Nodes should not connect to, nor gossip messages from, nodes on other networks.

Note: As of May 28, 2024 - perf testing is still in progress.

notes - This change should only affect path finding. No amendment needed. - Possible perf impact, but only back to old/previous behavior. Internal tracker: RPFC-105

`Testable`: - Notice that the bug snuck in and unit tests pass either way - that's not good. - It would be good to add a test case. Let's try...

@mtrippled : does this depend on other PRs, or could it be tested on its own?

(Ignore removing the label, that was a misclick.) Internal tracker: RPFC-104 notes - Normal performance test before release would catch any issue with this. - Does not require custom perf...