Add message sequencing and acknowledgment to remote messaging

[FUDCo]

Implements message acknowledgment and retransmission.

• Updates RemoteCommand type to include seq (sequence number) and ack (piggybacked ACK) fields
• Per-peer sequence tracking that persists across reconnections
• Implements timeout/retry logic with promise-based tracking

Closes #656

---

Note

Introduces reliable remote messaging with sequencing and acknowledgments, plus API and infrastructure updates.

• Switches sendRemoteMessage to accept RemoteMessageBase (object) instead of string across kernel, browser, and node runtimes; updates RPC payloads accordingly
• Adds handleAck and updateReceivedSeq methods and wires them through PlatformServices (browser/node) as fire-and-forget calls
• Extends RemoteHandle to parse seq/ack on inbound messages, call ACK handlers, and send base messages without local stringify
• Adds PeerConnectionState for per-peer state (seq tracking, pending queue) and revamps MessageQueue to store PendingMessage with capacity-based rejection
• Updates network layer to assign seq, piggyback ACKs, track/retry with timeouts, and improve reconnection/flush behavior; adds timeout guard to libp2p.stop()
• Updates Kernel/RemoteManager to forward RemoteMessageBase; removes auto-reply send on handler return
• Broad test updates (unit/e2e) and config tweaks (longer hook timeout, cleanup helpers); marks one flaky reconnection test as TODO

^{Written by Cursor Bugbot for commit 2a0f438. This will update automatically on new commits. Configure here.}