Fix issue with row id for non primary key tables (#3603)

# Description of Changes

When computing rowId for non primary key tables the typescript sdk
incorrectly used the entire data buffer.
This resulted in rowIds being incorrect when multiple rows were present
within an update.

# Expected complexity level and risk

1

# Testing

Tested this in the context of developing the collaborator feature on the
spacetime.com website.
Without this change, updates to tables without primary keys were
sometimes not applied to the client cache.
With this update no further issues were observed.

Co-authored-by: Tyler Cloutier <cloutiertyler@users.noreply.github.com>

Author: aasoni

crates/bindings-typescript/src/sdk/db_connection_impl.ts

@@ -293,6 +293,7 @@ export class DbConnectionImpl<
       const reader = new BinaryReader(buffer);
       const rows: Operation[] = [];
       const rowType = this.#remoteModule.tables[tableName]!.rowType;
+      let previousOffset = 0;
       const primaryKeyInfo =
         this.#remoteModule.tables[tableName]!.primaryKeyInfo;
       while (reader.remaining > 0) {
@@ -305,11 +306,12 @@ export class DbConnectionImpl<
           );
         } else {
           // Get a view of the bytes for this row.
-          const rowBytes = buffer.subarray(0, reader.offset);
+          const rowBytes = buffer.subarray(previousOffset, reader.offset);
           // Convert it to a base64 string, so we can use it as a map key.
           const asBase64 = fromByteArray(rowBytes);
           rowId = asBase64;
         }
+        previousOffset = reader.offset;
 
         rows.push({
           type,