feat(tests): add XEN tests

[jochem-brouwer]

🗒️ Description

This PR adds benchmark situations for the XEN mainnet contract.

🔗 Related Issues or PRs

Continuation of the now-closed PR in execution-spec-tests ethereum/execution-spec-tests#2101

✅ Checklist

Need to cleanup tests and add a test for reading existing slots, as well as writing zeros to a non-existing slot.

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx tox -e static

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered adding an entry to CHANGELOG.md.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).
• Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.
• Tests: For PRs implementing a missed test case, update the post-mortem document to add an entry the list.
• Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

Cute Animal Picture

[marioevz]

Hey @jochem-brouwer is this PR still required or could we close it? Thanks.

[jochem-brouwer]

Yes, this is rather awkward, I have commits at home which I should have pushed, these cover the "slow blocks" XEN scenarios. These are rather specific and not the "worst case scenarios" but I think at this point we want to include this type of "realistic" test, as it covers many parts of benchmarks (multiple account calls, multiple account writes, and multiple storage updates to different accounts) from a realistic scenarios.
I'll push them when at home.

[LouisTsai-Csie]

Hi @jochem-brouwer, any progress on XEN test? Is it ready for review 👍🏻

[github-actions]

This PR has had no recent activity and has been marked as stale.

[raxhvl]

Wondering if this is still relevant @jochem-brouwer

[jochem-brouwer]

It's not, the generic tests now target "worse worst" cases 😄 👍

I'll close (bit of nostalgia this one). Thanks @raxhvl 😄