test(kernel-node-runtime): fix flaky reconnection backoff e2e test

'handles reconnection with exponential backoff' timed out at 60s on
some runs. The vat's sendRemoteMessage helper re-redeems the ocap URL
on every call; with testBackoffOptions.ackTimeoutMs=2_000, the
RemoteHandle gives up on redemption after ~8s (ackTimeoutMs ×
(MAX_RETRIES + 1)) — too short for kernel2 to finish its restart path
(new DB connection + kernel init + libp2p + relay connection + vat
launch) under load.

Apply the same fix PR #927 used on the sibling tests: create a
reconnectOptions bag overriding ackTimeoutMs to 5_000 (20s window),
and thread it through both setupAliceAndBob and
restartKernelAndReloadVat.

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

Author: sirtimid

packages/kernel-node-runtime/test/e2e/remote-comms.test.ts

@@ -407,13 +407,22 @@ describe.sequential('Remote Communications E2E', () => {
     it(
       'handles reconnection with exponential backoff',
       async () => {
+        // ackTimeoutMs must be long enough for kernel2 to restart + reconnect
+        // before Alice's URL redemption gives up (fires after
+        // ackTimeoutMs × (MAX_RETRIES + 1)). See PR #927 for the same fix
+        // applied to sibling tests with this pattern.
+        const reconnectOptions = {
+          ...testBackoffOptions,
+          ackTimeoutMs: 5_000,
+        };
+
         const { aliceRef, bobURL } = await setupAliceAndBob(
           kernel1,
           kernel2,
           kernelStore1,
           kernelStore2,
           testRelays,
-          testBackoffOptions,
+          reconnectOptions,
         );
 
         const initialMessage = await sendRemoteMessage(
@@ -445,7 +454,7 @@ describe.sequential('Remote Communications E2E', () => {
           false,
           testRelays,
           bobConfig,
-          testBackoffOptions,
+          reconnectOptions,
         );
         // eslint-disable-next-line require-atomic-updates
         kernel2 = restartResult.kernel;