Add aptos-indexer-protos package for TS

[banool]

Summary

This PR does the following:

• Creates the aptos-indexer-protos package, which contains all the code generated from the protos, basic instructions for using them, a guide explaining how to publish the package, etc.
• Switches all the code under typescript/ to use this package. I modernize the packaging / tsc stuff as part of this.

I will update the proto generation stuff in the GH workflows in a later PR.

Callouts

Some things worth calling out that we might want to discuss:

• I have configured the generated code to represent u64s using bigint. Using string isn't very clear to the user and using number is dangerous.
• You must refer to types in the generated code using the absolute "path" through the modules, e.g. aptos.indexer.v1.GetTransactionsRequest). Through a long discussion with some TS experts this seemed like the best option while maintaining compatibility with various downstream development environments while also maintaining our own sanity: https://aptos-org.slack.com/archives/C03JJF9DJ4V/p1693414593545719.
• The getter and setter methods are gone from the generated code, it is just properties now. Imo this is cleaner and more modern but one downside is you have to null check yourself now, like transaction.user!. This is how it works in Rust too though so it's more standard this way.

Test Plan

I have tested that the library can be used from both commonjs and es code.

Testing our own example (commonjs):

$ cat /tmp/config.yaml
grpc_data_stream_endpoint: grpc.testnet.aptoslabs.com:443
grpc_data_stream_api_key: <token>
db_connection_uri: "postgresql://postgres:postgres@localhost:5432/example_event"
health_port: 8080
indexer_grpc_http2_ping_interval_in_secs: 30
indexer_grpc_http2_ping_timeout_in_secs: 5
starting_version: 0
chain_id: 2

cd typescript
pnpm build
node dist/processors/example-write-set-change-processor/processor.js process --config /tmp/config.yaml

{
  message: 'Successfully processed transaction',
  last_success_transaction_version: 39000n
}
{ message: 'Response received', starting_version: 40000n }
{
  message: 'Successfully processed transaction',
  last_success_transaction_version: 40000n
}
{ message: 'Response received', starting_version: 41000n }
{
  message: 'Successfully processed transaction',
  last_success_transaction_version: 41000n
}

[rtso]

I think we need this patch to fix an issue with the grpc-js library. More disucussion in https://aptos-org.slack.com/archives/C04PRP1K1FZ/p1683760992469519?thread_ts=1683670305.272199&cid=C04PRP1K1FZ

[banool]

Okay good to know, let me add it back.

[rtso]

Sweet, can we add a comment in this explaining what it's for? So we don't accidentally delete it later on

[rtso]

Why delete this?

[banool]

Well I'm not 100% sure why we had this in the first place but I think it was related to using an endpoint without TLS. We now have endpoints with TLS, so it's not necessary.

[rtso]

I think it might be to make it work with grpc-js patch. @jjleng would know better!

[jjleng]

no, this was not related to TLS. This is the settings we needed for the http2 flow control. Without these settings, the grpc link is very slow. With this, the link has similar performance as Python

[banool]

Okay got it, I'll try to make this work with TLS then.

[banool]

I'm having a bit of trouble getting this working, asking about it here: grpc/grpc-node#2565.

[rtso]

Do we have documentation on how to regenerate the protobuf types somewhere?

[banool]

Yeah in the top level README. I clean that up a bit further in the PR after this.