feat(tests): Port oog create refund test; add BAL >= Amsterdam

[fselmo]

🗒️ Description

I worked to port the test that caught this issue in the static tests as I think this was a good opportunity for porting while being able to add the BAL expectation for >= Amsterdam.

The parametrized case for code_deposit filled but failed BAL check against Amsterdam, still recording the writes.

This adds a fix as we should pass the appropriate parent call frame to the execute_code function so we can more appropriately track the merge_on_failure / merge_on_success part of the frame conclusion.

✅ 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: 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.
• Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

Cute Animal Picture

[gurukamath]

Instead of passing the parent_state_frame as a function parameter to process_message, would it be possible to recreate it within the function? I think process_message(message: Message) -> Evm is very clean as it stands. Alternatively, we could consider adding parent_state_frame to the Message dataclass (on similar lines as parent_evm)