feat(exceptions,specs): class to verify exception strings

[winsvega]

🗒️ Description

Extent exception mapper with base class so that any t8n can define exception string maps for any exception types

I put transaction exception validation into exception mapper for convinience atm.
Example exception message:

src/ethereum_test_exceptions/exception_mapper.py:84: in check_transaction
    raise Exception(
E   Exception: TransactionException (pos=1, nonce=0x1)
E   Error: exception mismatch:
E    want = 'Undefined' (TransactionException.TYPE_3_TX_INVALID_BLOB_VERSIONED_HASH),
E    got  = 'blob 0 has invalid hash version' (UndefinedException.UNDEFINED_EXCEPTION)
E    No message defined for TransactionException.TYPE_3_TX_INVALID_BLOB_VERSIONED_HASH, please add it to GethExceptionMapper
E    No exception defined for error message got, please add it to GethExceptionMapper

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

[marioevz]

I like the ExceptionMapper idea, I think it might be too t8n-focused but it could be used in many other places, e.g. exceptions from the Engine API when we run the tests in hive.

I think this PR can start with TransitionToolExceptionMapper defined in src/evm_transition_tool to make ExceptionMapper a bit more generic to open the door to future PRs to implement other subclasses.

[winsvega]

still need to setup other clients for this. but I refactored the suggestions. can check the code.
now I need to fill the exception strings for other tools.

Ah, and need to enable it for state tests

[marioevz]

Hey it's looking great overall, but I think we need to address the comments, mainly because the default t8n to fill tests has become the execution_specs t8n, so I think the exception mapper should be complete from the start.

[danceratopz]

This looks fantastic, looking forward to using these exceptions in consume in due course!

A few small comments below.

[marioevz]

Fixed tox. It turns out there was an invalid transaction in the framework tests.

[marioevz]

LGTM, thanks!