feat: Upgrade to 0.9.3 (NEAR Indexer Framework 0.10.0, refactor storing genesis records, more logs on indexer start)

[khorolets]

It should help to ensure the indexer is working and is going to start streaming and has not stuck

Also, bumped the version to 0.9.3 because of:

• upgrade to NEAR Indexer Framework 0.10.0
• change the logic of storing genesis records
• add more logs on indexer start
• include escape_json function to serializers

[frol]

I assume you checked that it works as expected :smile:

[khorolets]

I assume you checked that it works as expected 😄

I've checked it is working as expected with the localnet. It should work with others as well. Do you want me to extra check?

[frol]

I tested it with testnet genesis (5.4GB JSON file) on my local machine with local postgres database and it works great!

• peak RAM usage was 4.6GB, but it does not seem to be related to the indexer since while the genesis processing was happening, the RAM usage dropped down to 3.8GB and never go up
• time-wise it looks great!
  • 10 minutes to "Load config from" (not Indexer problem, nearcore does something heavy there)
  • 35 seconds to store accounts from genesis
  • 60 seconds to skip unrelated genesis records
  • 60 seconds to store access keys from genesis
• nearcore is not blocked by this storing the genesis data, which means that the implementation is async-friendly