Run verification of TTP events on full history

[tamirms]

To reduce the risk of bugs in the token transfer processor we can run the processor on all history.

For each ledger, we can check that the sum of all the asset movements derived from events is equivalent to the sum of all asset movements derived from ledger entry changes in the LedgerCloseMeta. See https://github.com/stellar/go/blob/0e69632de1e223dd72a68d01264e9d1e46773dc0/ingest/processors/token_transfer/verify_events.go for implementation.

@chowbao has suggested running the token transfer processor in stellar-etl to produce a full history token transfer table in big query.

when we include the TTP in stellar-etl we can simply invoke VerifyTtpOnLedger() along side the TTP. If VerifyTtpOnLedger() surfaces a discrepancy between the events and Tx Meta, we can fail the stellar-etl run on that ledger.

This method should provide a pretty comprehensive check on the correctness of TTP events derived from stellar classic operations. For TTP events derived from soroban transactions we will need to update the verification logic, that work is captured in #5625

[chowbao]

Events TTP backfill has run verifyEvents() and generated events from genesis to Feb 2024 (before soroban)

Next step is waiting for completion of SAC TTP events