Report an allocated IPv4 address that is not on the host

IPv6 works end to end between two machines; IPv4 silently did not, and the
agent said nothing useful about why.

Allocation moved the address from something derivable before startup to
something agreed at run time, so an interface configured by an earlier
`tun-setup` carries a different address than the one allocated. The kernel
then sends packets with that stale source and every peer drops them as not
belonging to us — correct behaviour, invisible cause. Meanwhile pings to
our own allocated address fall into the tunnel and land in the "nobody
owns this" counter.

The agent now checks whether its allocated address is assigned anywhere on
the host — by binding a UDP socket to it, which needs no privileges and no
platform code — and reports the exact `ip address add` command until it
is, mentioning that another address of the range has to go.

`tun-setup` no longer prints a derived IPv4 address, because that number
is now wrong by construction. It says the agent will print the real one.

The unroutable counter keeps one destination as a sample, in status output
too. A bare count says something is wrong; the address says what.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/dataplane/wireguard/tun.rs

@@ -130,6 +130,17 @@ impl TunDevice for MemoryTun {
     }
 }
 
+/// Whether an address is assigned to some interface on this host.
+///
+/// Binding a UDP socket to a specific address only succeeds when the address
+/// is local, which makes this a cheap check that needs no privileges and no
+/// platform-specific code. It does not say *which* interface has it, which is
+/// enough here: the agent chose the address, so anything else holding it is a
+/// problem in its own right.
+pub fn address_is_local(address: std::net::IpAddr) -> bool {
+    std::net::UdpSocket::bind((address, 0)).is_ok()
+}
+
 /// Creates [`MemoryTun`] devices.
 #[derive(Debug, Clone, Default)]
 pub struct MemoryTunFactory {