feat(tests): test all opcodes by fork

[winsvega]

🗒️ Description

define lists of opcodes by fork and verify that they are actually supported only at the allowed forks

🔗 Related Issues

PR ethereum/tests#1399

✅ Checklist

• All: Set appropriate labels for the changes.
• All: Considered squashing commits to improve commit history.
• All: Added an entry to CHANGELOG.md.
• All: Considered updating the online docs in the ./docs/ directory.
• Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
• Tests: A PR with removal of converted JSON/YML tests from ethereum/tests have been opened.
• Tests: Included the type and version of evm t8n tool used to locally execute test cases: e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
• Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

[winsvega]

I put def test_cover_revert(state_test: StateTestFiller, pre: Alloc):
there to prove that no coverage lost. but is it ok if the coverage is red, and it merged with explanation?

here the coverage is red because in original test there were some failing transactions due to invalid stack for opcodes, and create opcodes didn't work as intended, also transaction was running as creatte instead I use call contracts here.

[danceratopz]

LGTM - nice test!

Added a few minor suggestions below, mainly just style and clearer docstrings.

Also added a framwork test to check that we cover the full possible opcode range: bfc84a5

[marioevz]

One single comment, but I think it could be left for a follow up PR, and we could merge this one as is (after Dan's comments). Thanks!

[danceratopz]

LGTM! Added a follow-up ticket for @marioevz's idea to extend the Opcode (or Bytecode) class with supported_evm_code_types #770.