feat(fw): Call evmone-eofparse on EOF tests filling

[marioevz]

🗒️ Description

Adds EOF exception checking using evmone-eofparse tool. Prints a nice message now if expected exception does not match returned by evmone or if valid eof test fails on evmone and so on.

🔗 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: 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]

this PR consumes #516 that introduced this feature example use

[shemnon]

It would be nice if this could be made generic in a manner like TransitionTool is made generic, I expect each client to expose their own tool.

Also, I would like a format that accepts required arguments. Besu's equivelant is evmtool code-validation and that won't pass the binary string matching task ask it is a binary plus an argument.

Combine this with the fork being validated possibly being another argument.

[marioevz]

It would be nice if this could be made generic in a manner like TransitionTool is made generic, I expect each client to expose their own tool.

Also, I would like a format that accepts required arguments. Besu's equivelant is evmtool code-validation and that won't pass the binary string matching task ask it is a binary plus an argument.

Combine this with the fork being validated possibly being another argument.

I think @danceratopz might know a bit better than I do how to implement something along these lines.

We might need to create another package like we currently have evm_transition_tool, maybe a eof_tool with all different flavors of EOF tools implemented.

We might also need to implement new parameters to configure it in the pytest_plugins/test_filler.

My main ask when we implement this is that the normal test filling process does not fail if there no eof tool installed, only fails if we are trying to fill an EOF test.

[winsvega]

we stick to evmone-eofparse for verification for now till later when we refactor tooling capture and expection verification

[danceratopz]

Very nice.

Really like how/where eofparse is called, I had a mental block on this one and wanted to add it to the FixtureCollector - it's much more logical in the fixture generator for this use case!

Love the exceptions raised by verify_fixtures() - really clear.

After aligning with @winsvega, I've refactored the code a bit in #538, which addresses the small concerns below. Please let me know what you think.

From the above comment from @shemnon:

It would be nice if this could be made generic in a manner like TransitionTool is made generic, I expect each client to expose their own tool.

We will definitely do this! But will add this work in a separate PR as it requires quite a bit of code organization. Don't want to block this helpful addition though, so we should get this merged first.

[danceratopz]

My main ask when we implement this is that the normal test filling process does not fail if there no eof tool installed, only fails if we are trying to fill an EOF test.

@marioevz, Regarding this, we warn at the end of the test session if evmone-eofparse was not found: