feat: run Aptos indexer processors v2 against locally running Movement network

[andygolay]

Summary

Addresses movement repo issue #1259 (sub-issue of #1258).

I'm working on it in this repository because I was having issues with adding the processor v2 directly into the movement repo and thought a standalone repo might work better.

To run the processors:

1. In the movement repository branch feature/da-sequencer-node run nix develop then just movement-full-node native build.setup.indexer --keep-tui to start the local network and the postgres db and expose the indexer gRPC endpoint.

2. Prepare to send transactions locally, for the indexer to process. This needs to be done fairly quickly after the next step, or else the request for chain ID will time out and the processor will stop.

3. On the branch for this PR, run

cd examples/postgres-basic-events-example && ./run-processor.sh events_processor

4. Send transactions on local network and verify that the processor is indeed processing them.

Outstanding Issues

• I'm not sure what is the best way to run all of the processors in parallel. From what I can tell, the needed processors are:

  • user_transaction_processor
  • account_transactions_processor
  • token_v2_processor
  • fungible_asset_processor
  • default_processor
  • ans_processor
  • stake_processor
  • objects_processor
  • monitoring_processor
  • gas_fee_processor
  • account_restoration_processor

• It may or may not be necessary to integrate this into the movement repository... still working on understanding the structure of how this will be deployed.