fix(kernel-node-runtime): increase MAX_QUEUE test timeout to 120s

The "rejects new messages when queue reaches MAX_QUEUE limit" test
sends 201 messages while disconnected, restarts a kernel, and resolves
all promises. In CI this can take >90s. Bump from NETWORK_TIMEOUT*3
(90s) to NETWORK_TIMEOUT*4 (120s) to avoid flaky timeout failures.

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

Author: sirtimid

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

@@ -636,7 +636,7 @@ describe.sequential('Remote Communications E2E', () => {
         const newMessage = kunser(newMessageResult);
         expect(newMessage).toBe('Sequence 999 received');
       },
-      NETWORK_TIMEOUT * 3,
+      NETWORK_TIMEOUT * 4,
     );
   });