Fix Rosetta under-reporting balance-change operations for zkApp commands that apply the same account update more than once. Identical account updates are content-deduplicated into a single `zkapp_account_update` row, so a command's `zkapp_account_updates_ids` array can repeat an id — each occurrence being a distinct on-chain application. The `/block` and `/search` queries joined that array with `zau.id = ANY (zc.zkapp_account_updates_ids)`, which matches a repeated id only once and therefore collapsed N occurrences into a single account update, dropping the other N-1 balance-change operations. Affected blocks reconciled short by the missing operations' total, showing up as balance drift in `rosetta-cli check:data`. The `= ANY` join is replaced with `LEFT JOIN LATERAL unnest(...) WITH ORDINALITY ... ON true`, which expands the array positionally so every occurrence yields its own account update, ordered by array position; the `LATERAL ... ON true` form preserves fee-payer-only commands, whose array is empty or NULL. Adds a regression test to the Rosetta indexer test suite that inserts a zkApp command repeating an account-update id and asserts one account update per array element.
