Microblock data missing from event emitter while syncing

[zone117x]

While syncing with an existing network (as in not just running against a private-testnet miner), the /new_microblocks endpoint is never called. The current payload in /new_block doesn't contain enough information to process microblock data.

Specifically, the following information about each transaction in/new_block is not available and there's no way for the API to derive it:

{
  microblock_sequence: number;
  microblock_hash: string;
  microblock_parent_hash: string;
}

It also might not be possible for the API to derive a microblock transaction tx_index (just the logical ordering of txs within a microblock), depending on how the current tx_index property is being set in the /new_block payload.

This is a blocker for microblock support, and also a blocker for testing the API's handling of real micro-orphaning behavior in a mainnet/testnet network.

[zone117x]

Note: ideally these changes should be made to this branch #2653 which includes fixes for other microblock blockers

[zone117x]

This issue is fixed when running against a node with this change 7022cf9

However, it does look like the tx_index logical ordering issue described above is a problem. It looks like tx_index should probably be aded to the StacksTransactionReceipt struct and set while iterating microblock txs inside process_microblocks_transactions and while iterating anchor block/batched transactions inside process_block_transactions.