[CLI] Add support for running standard indexer processors to the local testnet

[banool]

Stack

• Previous in stack: [CLI] Add support for running postgres in a container to the local testnet + rest of PRs in stack #10271
• Next in stack: [CLI] Add support for not JSONifying errors #10310

Description

This PR adds support for running indexer processors to the local testnet. The processors you run is configurable with --processors, which uses the new ProcessorName enum.

Note: I will update the dependency from that branch to a specific rev later.

Test Plan

cargo run -p aptos -- node run-local-testnet --assume-yes --force-restart --with-indexer-api

Readiness endpoint: http://0.0.0.0:8070/

Postgres is starting, please wait...
Transaction stream is starting, please wait...
Node API is starting, please wait...
Faucet is starting, please wait...

Completed generating configuration:
        Log file: "/Users/dport/.aptos/testnet/validator.log"
        Test dir: "/Users/dport/.aptos/testnet"
        Aptos root key path: "/Users/dport/.aptos/testnet/mint.key"
        Waypoint: 0:2cc2b83a3435b6b38f5f8ef84afe96aef2458c524445d3d72cd55b0459e627c5
        ChainId: 4
        REST API endpoint: http://0.0.0.0:8080
        Metrics endpoint: http://0.0.0.0:9101/metrics
        Aptosnet fullnode network endpoint: /ip4/0.0.0.0/tcp/6181
        Indexer gRPC node stream endpoint: 0.0.0.0:50051

Aptos is running, press ctrl-c to exit

Node API is ready. Endpoint: http://0.0.0.0:8080/
Postgres is ready. Endpoint: postgres://postgres@127.0.0.1:5433/local_testnet
Transaction stream is ready. Endpoint: http://0.0.0.0:50051/
Faucet is ready. Endpoint: http://127.0.0.1:8081/

Applying post startup steps...

Setup is complete, you can now use the local testnet!

local_testnet-# \x
Expanded display is on.
local_testnet-# select * from events limit 1;
ERROR:  syntax error at or near "select"
LINE 2: select * from events limit 1
        ^
local_testnet=# select * from events limit 1;
-[ RECORD 1 ]------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sequence_number          | 3
creation_number          | 3
account_address          | 0x0000000000000000000000000000000000000000000000000000000000000001
transaction_version      | 4
transaction_block_height | 3
type                     | 0x1::block::NewBlockEvent
data                     | {"hash": "0x1cce75abaf027f116439ef26040f64f6d5337f6a04f0b093bed08a51b3da5981", "epoch": "2", "round": "2", "height": "3", "proposer": "0xa03f668876e2ec4d37d3b7f33ad29b5d01c777a189c2dfc0b03d67046c19c7d9", "time_microseconds": "1695901972557097", "failed_proposer_indices": [], "previous_block_votes_bitvec": "0x80"}
inserted_at              | 2023-09-28 11:52:53.356014
event_index              | 0

local_testnet=#

I also tested that works when using --with-host-postgres:

cargo run -p aptos -- node run-local-testnet --assume-yes --force-restart --with-indexer-api --postgres-user $USER --use-host-postgres

[0xmigo]

LGTM

I will let Greg or Bowen to double check on indexer processor stuff.

[0xmigo]

Clap with default values - This is convenience! TIL

[0xmigo]

nit - Personally I would add the unsupported processor into a set, then check from the list/set.