new(tests): CALLF with truncated immediate bytes

[chfast]

🗒️ Description

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

you can also repeat the imm_from_next_section case with a byte in the data section - even better if it's the data section of the parent container, not unlike the bug which Danno's fuzzing found recently.

But maybe that would be too much

[chfast]

Adding raw bytes to bytecode strikes back. I need to check what is the best solution so far.

[chfast]

you can also repeat the imm_from_next_section case with a byte in the data section - even better if it's the data section of the parent container, not unlike the bug which Danno's fuzzing found recently.

But maybe that would be too much

This test is quite sophisticated: if you overflow reading of one section to the next one the validation will pass. This only works for the CALLF + "00" case. Therefore, I'm going to pass on parametrizing it.