feat(plugins,fixtures,specs): Labeled fixture and execute formats

[marioevz]

🗒️ Description

Labeled Fixture Formats in Spec Types

Adds labeled fixture and execute formats that can be defined by the spec tests for the fixtures they produce.

For example, state_test generated Blockchain and Blockchain engine fixtures now have the following labels:

• LabeledFixtureFormat(BlockchainFixture, "blockchain_test_from_state_test")
• LabeledFixtureFormat(BlockchainEngineFixture, "blockchain_test_engine_from_state_test")

This translates in the test IDs now showing "blockchain_test_from_state_test" and "blockchain_test_engine_from_state_test" instead of "blockchain_test" and "blockchain_test_engine" respectively.

These test cases now also have an extra marker that is the label.

• blockchain_test_from_state_test and blockchain_test markers for Blockchain test.
• blockchain_test_engine_from_state_test and blockchain_test_engine markers for Blockchain test.

This enables a bit more granularity when selecting the cases to fill (or execute in the case of execute), as we don't lose the -m blockchain_test, instead we now also can use -m blockchain_test_from_state_test to only fill blockchain tests that were generated from a State test.

I.e. -m blockchain_test still selects Blockchain tests generated from state tests, but we now also have -m blockchain_test_from_state_test which selects only Blockchain tests that were generated from a state test.

Remove StateTestOnlyand BlockchainTestEngine

Removes StateTestOnly and BlockchainTestEngine (and EOFTestOnly after #783) classes in favor of using markers to signal that a test should only be filled for a given fixture format:

• pytest.mark.state_test_only
• pytest.mark.blockchain_test_only
• pytest.mark.blockchain_test_engine_only
• pytest.mark.eof_test_only in feat(specs): EOF: eof_test generates state tests, and execute in live devnets #783

This makes it easier to add the marker to a single parameter during parametrization, instead of having to write a new test function to single out tests that have this requirement.

Notes

Required for #783.

🔗 Related Issues

✅ 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.

[spencer-tb]

Nice PR. Easy to see what's going on. Only a few thoughts but nothing major!

Approved and LGTM (as I would be happy to merge as is)!

[spencer-tb]

Ohh and I'm being pedantic but could we add a changelog entry too 😅