iroh 1.3, and a socket that survives a service restart

iroh 1.0.2 -> 1.3.0 (relay reconnects that keep answering, rate-limit
notices from relays, the n0 DNS resolver with configurable fallbacks,
relay connection metrics), iroh-mdns-address-lookup 0.4 -> 0.6,
n0-future 0.1 -> 0.3. No code changes were needed; the suite passes.

varde.service now keeps /run/varde across restarts
(RuntimeDirectoryPreserve=yes): stopping the service removed the
directory and with it the socket unit's file, leaving varde.socket
"active" on an unlinked path after any service restart. The install
notes say to restart the socket, which cycles both.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

varde-daemon/Cargo.toml

@@ -19,10 +19,10 @@ iroh-blobs = { workspace = true }
 # Request::Put / Read carry content inline, base64.
 base64 = "0.22"
 # mDNS/local-network address lookup left iroh core in 1.0.
-iroh-mdns-address-lookup = "0.4"
+iroh-mdns-address-lookup = "0.6"
 # Interop with iroh-blobs streams and channels; both are already in the
 # dependency tree via iroh-blobs.
-n0-future = "0.1"
+n0-future = "0.3"
 irpc = "0.17"
 # Feature-gated D-Bus client for NetworkManager metered status.
 zbus = { version = "5", optional = true, default-features = false, features = ["tokio"] }