fix: sort interfaces according to likely reachability

[gmaclennan]

the getRemoteBaseUrls() function reads all network interfaces and returns the ipv4 address for all non-internal interfaces, since we don't know which interface may be accessible from the peer device trying to connect.

However, we can take a guess at which interface is most likely to be accessible to a peer, and list that one first, which means it will be tried first and hopefully result in faster connections.

This is an attemp to address an issue where an interface rndis0 on Android was being listed first, and is unreachable to the peer, but it was taking 130s to timeout before trying the next IP. rndis0 is an interface created by android for USB tethering.

[gmaclennan]

superseded by #53

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (cca06a0) to head (4339c92).

Additional details and impacted files

@@    Coverage Diff     @@
##   main   #52   +/-   ##
==========================
==========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.