Add get_transaction_status to chain_plugin

[oschwaldp-oci]

Adding a feature that allows querying the status of a transaction on the chain.

Support for the feature added in cleos via subcommand: get transaction-status <transaction_id>

Feature takes a transaction_id as input and outputs chain status and, if available, transaction status in the following format:

{ "state": "IN_BLOCK", "block_number": 90, "block_id": "0000005accfd59ba80a05380f60d51687406337b2aedd28b7daa33fdb8c16b5a", "block_timestamp": "2022-04-27T16:11:26.500", "expiration": "2022-04-27T16:11:56.000", "head_number": 186, "head_id": "000000bab27da51f76f483bb629b532510c22e2eb1acc632f5b37b421adecf63", "head_timestamp": "2022-04-27T16:12:14.500", "irreversible_number": 25, "irreversible_id": "0000001922118216bc16bf2c60d950598d80af3beca820eab751f7beecdb29e4", "irreversible_timestamp": "2022-04-27T16:10:54.000", "last_tracked_block_id": "000000129cee97f3e27312f0184d52d006a470f0e620553dfb4c5b4f3c856ab2" }

Transaction Status:

• If the transaction is unknown, failed (expired), in a block, rolled back, finalized, or limited in block (this would be for unknown trans ids that the controller knows about). This will be reported as state with values of: UNKNOWN, FAILED, FORKED_OUT, LOCALLY_APPLIED, IN_BLOCK, IRREVERSIBLE.
• The transaction’s block number, id, and timestamp, if they are applicable, will be reported as block_number, block_id, and block_timestamp. The transaction’s expiration date as expiration

Chain Status:

• The current head block number, id, and timestamp will be reported as head_number, head_id, and head_timestamp.
• The irreversible block number, id, and timestamp will be reported as irreversible_number, irreversible_id, and irreversible_timestamp.
• The _last_tracked_block_id, from the chain state object as last_tracked_block_id