fix: correct array txid handling in electric collection handlers

The bug was in processMatchingStrategy when handling arrays of txids.
Using `.map(awaitTxId)` directly caused Array.map() to pass three
arguments (element, index, array), and the index was being interpreted
as the timeout parameter of awaitTxId.

For example:
- awaitTxId(txid1, 0) → timeout 0ms (immediate timeout!)
- awaitTxId(txid2, 1) → timeout 1ms (immediate timeout!)

This caused TimeoutWaitingForTxIdError even though the txids were
being sent correctly via the sync stream.

The fix uses an arrow function to ensure only the txid is passed:
await Promise.all(result.txid.map((txid) => awaitTxId(txid)))

This allows the timeout to use its default value of 5000ms.

Fixes #793

Author: claude

packages/electric-db-collection/src/electric.ts

@@ -506,7 +506,8 @@ export function electricCollectionOptions(
     if (result && `txid` in result) {
       // Handle both single txid and array of txids
       if (Array.isArray(result.txid)) {
-        await Promise.all(result.txid.map(awaitTxId))
+        // Use arrow function to avoid passing map's index as timeout parameter
+        await Promise.all(result.txid.map((txid) => awaitTxId(txid)))
       } else {
         await awaitTxId(result.txid)
       }

packages/electric-db-collection/tests/electric.test.ts

@@ -697,7 +697,7 @@ describe(`Electric Integration`, () => {
             },
             { headers: { control: `up-to-date` } },
           ])
-        }, 50)
+        }, 1)
 
         setTimeout(() => {
           subscriber([
@@ -711,7 +711,7 @@ describe(`Electric Integration`, () => {
             },
             { headers: { control: `up-to-date` } },
           ])
-        }, 100)
+        }, 2)
 
         // Return array of txids - this is the pattern that's failing
         return { txid: txids }