Allow for using block_api.get_block API

[eonwarped]

Prepares for eventual deprecation of condenser_api.get_block.

• Handle new output format (inner block parameter)
• Handles HIVE/HBD nai assets used in transfer op and commentOptions op
• Reformatting beneficiaries in commentOptions to match old API

Moves a few configurable options to config:

• hashVerificationNode - string or false, default value is false. Whether to tail a different hive engine API and check for hash match before committing a block to the DB. Example of a valid value to enable this feature would be "https://api.hive-engine.com/rpc/blockchain"
• streamerOptions.antiForkBufferMaxSize - int, default value is 2. The number of blocks to check ahead to confirm same fork before sending block for processing
• streamerOptions.maxQps - int, default value is 1. Max queries to send at a time per node in config
• streamerOptions.lookaheadBufferSize - int, default value is 5. Number of blocks to fetch at a time using all nodes in config. Note that if any node in the config is unresponsive it can cause the block fetching to stall.
• streamerOptions.useBlockApi - boolean, default value is false. Whether to use block_api get_block as opposed to condenser_api.get_block which is deprecated.

Also

• Minor fixes to debuggability (hash verification mode)

[bt-cryptomancer]

It looks like you've changed the enableHashVerification setting to hashVerificationNode, but forgot to make the corresponding update to config.example.json.

Also, can you please document on the PR what each of the new streamerConfig settings is for, and confirm that the default values you've selected are good values for production use (so node operators can simply copy the example when upgrading)?

[eonwarped]

It looks like you've changed the enableHashVerification setting to hashVerificationNode, but forgot to make the corresponding update to config.example.json.

Also, can you please document on the PR what each of the new streamerConfig settings is for, and confirm that the default values you've selected are good values for production use (so node operators can simply copy the example when upgrading)?

Done with config. Updating PR.

[bt-cryptomancer]

Thanks, looks good now.