The TransportReader/Writer's dispose() method should handle that, and
ConnectionManager is responsible for calling it.

Because that's what it does.

We don't need two separate executors for long-running IO threads.

Fixed a bug in SimplexMessagingIntegrationTest that should've caught
this.

This should enable us to connect to contacts faster at startup and
whenever a new means of connecting becomes available.

The LAN plugin only accepts IPv4 link-local or site-local addresses.
This rules out LANs that use globally routable addresses (such as UCL),
but also reduces the chances of the LAN plugin making observable
connections across the WAN, which could reveal the social graph.

Both plugins will attempt to reuse the previous address and port only if
there's currently an interface with that address; this will avoid
unnecessary attempts to bind to nonexistent addresses.

Of course, not all devices support Bluetooth...

This allows the oldest LocalAuthor to be used as the default.

This adds complexity but will save a lot of bandwidth, as most of the
strings and byte arrays we want to send are less than 128 bytes.

The extra complexity isn't exposed outside of the serial component.