feat(test-benchmark): add terminating opcode benchmark

[LouisTsai-Csie]

🗒️ Description

Add new benchmark test for repricing analysis:

• POP
• INVALID, RETURN, REVERT, STOP

🔗 Related Issues or PRs

None

✅ Checklist

• 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.33%. Comparing base (2c83b84) to head (f84c2b2).

Additional details and impacted files

@@               Coverage Diff                @@
##           forks/amsterdam    #2027   +/-   ##
================================================
  Coverage            86.33%   86.33%           
================================================
  Files                  538      538           
  Lines                34557    34557           
  Branches              3222     3222           
================================================
  Hits                 29835    29835           
  Misses                4148     4148           
  Partials               574      574           

Flag	Coverage Δ
unittests	86.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[marioevz]

Some comments, thanks!

[marioevz]

Would it be worth it here to create a "from max stack height" version here?
One where we first push fork.max_stack_height() elements, then pop them all and repeat?

[marioevz]

Suggested change

	elif opcode.popped_stack_items > 0:
	attack_block = opcode(Op.PUSH0, return_size)
	elif opcode.kwargs == ["offset", "size"]:
	attack_block = opcode(offset=Op.PUSH0, size=return_size)

It's a tiny bit more explicit.

[marioevz]

In this case we are testing moving funds to a warm account, but would it be worth it to send to a cold and new account in another version of this test?

We can make the ExtCallGenerator send 1 wei with each call so that the selfdestruct actually has an effect too.

Perhaps self-destruct deserves its own test function.