new(test) Stack validation in CALLF

[shemnon]

🗒️ Description

Add a test to cover cases where stack would not overflow but CALLF stack
reservation rules would cause a revert.

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

[pdobacz]

LGTM, minor comments. Do we need to also update eof_tracker.md? I'm not sure but maybe Max stack size (1024) in CALLF-ed function was covering this case, please double check though, I didn't analyze it

[pdobacz]

gas_price and protected can be left out

[pdobacz]

Suggested change

	pytest.param(1020, 1, 3, False, id="1020"),
	pytest.param(1021, 1, 3, True, id="1021"),
	pytest.param(1020, 1, 3, False, id="success"),
	pytest.param(1021, 1, 3, True, id="failure"),

if we just have these two now (do I understand correctly, the intention is that 1022 would not validate anymore? Or are there other combinations of params which would validate and make sense to test?

[shemnon]

The essential test is pass below, and fail above. I was considering messing with the input/output levels, but determined it was not essential to the test. I took input and output of the params, and just have stack size and wether we expect failure. Seemed to communicate intent better than embedding what a failure is into the text code.

[shemnon]

Added another tests to check CALLF when stack is at max ("rule #4") - by EIP this should revert, but there are ways it would succeed without the check, so we need to do one of those ways and then test it.