feat(vm): EVM active precompiles (backport #7)

[mergify]

This is an automatic backport of pull request #7 done by Mergify.
Cherry-pick of e61d503 has failed:

On branch mergify/bp/release/1.10/pr-7
Your branch is up to date with 'origin/release/1.10'.

You are currently cherry-picking commit e61d503bf.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   CHANGELOG.md
	both modified:   core/state_transition.go
	both modified:   core/vm/contracts.go
	both modified:   core/vm/evm.go
	both modified:   core/vm/runtime/runtime.go
	both modified:   eth/tracers/js/goja.go
	both modified:   eth/tracers/native/4byte.go
	both modified:   internal/ethapi/api.go
	both modified:   tests/state_test.go

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[facs95]

Fixed the conflicts - please check d52d91d and 719e9d3 to see what had to be done just to make sure you agree with the changes

[Vvaradinov]

@facs95 changes LGTM.