feature: Protos

[gbarkhatov]

• Adds compiled protobuf files to src/proto
• If we want to update them - just download the latest git repo, put babylon at the top level and run npm run build:proto

[totraev]

Any reason to use this particular plugin? It generates a lot of duplicated data which will blow up our bundle size. From the another hand default plugin only generates schemas + types which can be used together with fromBinary method

[jrwbabylonlab]

Agree with David on this

[gbarkhatov]

@totraev @jrwbabylonlab
We can configure our protobuf files generation in multiple ways. The reason I chose this approach is

• it's the easiest, generates everything
• it was already established and working on btc-staking-dashboard application
  It leads to https://i.imgur.com/lK7Xr86.png, generates all the types for the dependencies, etc.

We can play around with config on https://github.com/babylonlabs-io/babylon-proto-ts

@totraev I am not sure whether or not usage of .fromBinary will be handy or that the current approach bloats the bundle size. But you can create an issue on that repo describing the pros of the suggested approach in comparison with the current that is already set up

[jrwbabylonlab]

nit: i think this can be simplified to npx buf generate "$PROTO_DIR" ?

[jrwbabylonlab]

would be nice t perform this clean up even if any of the above command were failed/existed.
try with trap?

trap 'rm -rf "$PROTO_DIR" "$BABYLON_REPO_DIR"' EXIT

[gbarkhatov]

Minor update - this PR might be not needed as we move to the npm library and a separate repository

[gbarkhatov]

Closing this in favor of babylon-proto-ts