Cherry picking to target branch release/v1.13.14-0.1.0.rc.3

[darioush]

From @ARR4N:

• See feat: release-branch automation #137
• The base branch needs to be changed because it's currently main but that can wait until you create the release/v... branch so it's not just sitting there
• params/version.libevm.go needs to be updated

[ARR4N]

We need to only do cherry picking in release branches so they can be dropped once the original is included in the main branch. Ok for testing / communication of requirements, but please don't merge it otherwise we'll have problems later when there are two copies.

[qdm12]

d10c4a3 is in #114 - can we close this PR?
I don't think a8ffd92 is needed for the coreth x libevm to work right?

[darioush]

I don't think a8ffd92 is needed for the coreth x libevm to work right?

At least some UTs fail, if I recall correctly, you are welcome to try ofc as I could be wrong

[qdm12]

I took the liberty to recycle this branch and PR to target the release/1.13.14-0.1.0.rc.3 branch.
I rebased this one on the main branch, cherry-picked geth commit ethereum@69f815f and forced-push it here.

We should keep this branch rebased at the tip of the main branch until we want to do this rc.3 release.

[ARR4N]

I would prefer that we use a fresh PR for the release branch. This has so much irrelevant history and an irrelevant source branch name.

[qdm12]

Replaced by #142 thanks @ARR4N !