v1/chore(web3-eth-accounts): bump @ethereumjs/common and @ethereumjs/tx

[legobeat]

Description

The versions of @ethereumjs/ dependencies were pinned in #5529.

This retains the pin (uncertain why it was first introduced) but bumps them to latest within semver-major.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

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.
  • Note: I do get a bunch of lint errors but these are unrelated and present on the base branch.
• 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.
  • This script does not exist on the 1.x branch.
• 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.

[legobeat]

@spacesailor24

[jdevcs]

We dnt merge external PRs with following changes:

• dist/ build output

• package-lock files, ( If changes in packagelock are necessary thn one of our team member will do these in another PR )

[Muhammad-Altabba]

Hi @legobeat
Did you face an issue that needed to update dependencies, in order to be fixed?
Thanks,

[legobeat]

Hi @legobeat Did you face an issue that needed to update dependencies, in order to be fixed? Thanks,

Yes: To get the updates done in the updates in @etehreumjs/common, for example https://github.com/ethereumjs/ethereumjs-monorepo/releases/tag/%40ethereumjs%2Fcommon%402.6.5. Is there any reason to keep them frozen at legacy version?

[Muhammad-Altabba]

Thanks @legobeat for your contribution,