TxnType is not returned in JSON-RPC response

[flavor-town]

Description

The transaction type is not returned in the json-rpc reponse leading to in correct client hash calculations.
Default TxType is 0 = LegacyTx.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes

The transaction response now includes a type field, which will tell the end user if the txn is a LegacyTx, StateTx, or DynamicFeeTx. I believe this is required for EIP1559 txns to be processed and displayed correctly.

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

[Stefan-Ethernal]

Pay attention to this failing unit test: TestBlock_Encoding. Otherwise looks good.