[meta] Update NEAR Proto definitions for the latest Firehose types

[azf20]

The type definitions have been updated for the NEAR firehose. In order to migrate to the latest version, we need to make the Graph Node and graph-ts types compatible too

• [x] Add types to Graph Node
• [x] Update hosted service configuration (near-mainnet, add near-testnet) & handle switch-over

[maoueh]

Here the upgrade plan:

• We are going to run aside our current set of micro-services as v2 version of all the required components
• Well before the update, we will create mainnet-v1.near.streamingfast.io that will serve v1 (it will be at that time a "symlink" to mainnet.near.streamingfast.io
• Hosted service will be update to use mainnet-v1.near.streamingfast.io
• We will decide on a switch date, at that time:
  • We will change mainnet.near.streamingfast.io to point to v2 components
  • Hosted service will be updated to correct graph-node version that supports the new v2 protobuf format at that same time the config will be updated again to point back to mainnet.near.streamingfast.io.
  • On reboot, everything should continue to work as expected, otherwise, if we revert, we need to revert the version as well as the config
• After everything has been stabilized, we will kill our v1 infra and delete the mainnet-v1.near.streamingfast.io

[azf20]

This sounds good @maoueh - let us know when the v1 symlink is in place and we can make the config update

[azf20]

We will also add testnet support at the same time as this switch-over, assuming the endpoint is ready cc @sduchesneau

[maoueh]

To fix an issue when dealing with undo on Near, we will need to add a field previous_block_height in the protobuf definition so we are able to fully reconstruct the parent ptr when a block is undo.

This means we will need to reprocess again so we will need to post-pone a bit the upgrade.