Support External Indexer via gRPC AcceptedSubscriber + Optional Internal Indexing about hypersdk

[gbartolome-avax]

Per Slack conversation with @aaronbuchwald Data Platform would archive HyperSDK payloads using a similar pattern we use now when we ingest our EVM based subnets into our Data Lake

It will depend on a subscriber based producer/consumer push pattern.

1. parent consumer will subscribe to HyperSDK messages and push messages to a messaging stream, in this case Kafka
2. child consumers will subscribe to HyperSDK Kafka topic for all payloads

[aaronbuchwald]

Linking a few relevant issues here:

Export Block/Tx/State Diffs to External Store

#961

I think the best way to support block/tx indexing is with this accepted subscriber pattern. Exporting state diffs would be a change from the current interface that we could optionally support if needed. Depending on the VM and use case, this may push a lot of data, so I'd prefer to export state diffs to an external store if the need arises rather than prioritizing it and changing the code to support it now.

If this is completed w/o exporting state diffs to an external store, we should open a new GitHub issue for state diffs as a potential future improvement.

Support S3 Archiver

#531
#697

This would be great to support. To avoid feature bloat in the HyperSDK, I'd prefer an S3 archiver implementation to be implemented as an external service to the HyperSDK using the gRPC Accepted Subscriber.