feat: make getEthereumjsTxDataFromTransaction not trim extra fields

[nicolasbrugneaux]

Description

This PR refactors getEthereumjsTxDataFromTransaction to not trim extra fields anymore whilst still aliasing input and gasLimit

Type of change

• New feature (non-breaking change which adds functionality)

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run lint with success and extended the tests and types if necessary.
• I ran npm run test:unit with success.
• I ran npm run test:coverage and my test cases cover all the lines and branches of the added code.
• I ran npm run build and tested dist/web3.min.js in a browser.
• I have tested my code on the live network.
• I have checked the Deploy Preview and it looks correct.
• I have updated the CHANGELOG.md file in the root folder.
• I have linked Issue(s) with this PR in "Linked Issues" menu.

[ Closes #7273 ]

[nicolasbrugneaux]

I also took the opportunity to modify SomeNewTxTypeTransaction class to have a custom field so we can kinda e2e tests plugins using custom fields through customTransactionSchema

[jdevcs]

@nicolasbrugneaux could you pls test dev release https://www.npmjs.com/package/web3/v/4.13.1-dev.cc99825.0?activeTab=versions in your app.

[nicolasbrugneaux]

@nicolasbrugneaux could you pls test dev release https://www.npmjs.com/package/web3/v/4.13.1-dev.cc99825.0?activeTab=versions in your app.

Hello! I was OOO for a couple of days. I'll get right on testing that.

[nicolasbrugneaux]

Had to adjust a little bit my dependencies, but it worked wonders, I suppose once they're all released as latest it won't be necessary to play with resolutions anymore.