Implement a way to identify fixtures outside of tests/prague/eip7692_eof_v1 that test EOF

[marioevz]

Raised by @pdobacz in #754 (comment), we need a way to efficiently select tests that verify EOF and are outside of the main tests folder (tests/prague/eip7692_eof_v1) but still produce EOF V1 code.

E.g. tests that use the @pytest.mark.with_all_evm_code_types decorator to automatically fill in both legacy and EOF modes, because these tests remain in the respective EIP folder but also exercise EOF code paths.

[pdobacz]

Hey, do I understand correctly, that before we solve this there is no way to include such tests (EOF-wrapped MCOPY tests for example, as the PR linked) in the eip7692 pre-releases?

Could we just put them under the state_tests/cancun/eip5656_mcopy? as long as they're in the eip7692 pre-release and consumers just run everything in state_tests, and the actual target fork (Osaka) is in the JSON anyway, that could work maybe?

[marioevz]

Could we just put them under the state_tests/cancun/eip5656_mcopy? as long as they're in the eip7692 pre-release and consumers just run everything in state_tests, and the actual target fork (Osaka) is in the JSON anyway, that could work maybe?

Yes I think this could be the quick solution to this, simply fill everything using the Osaka fork.