feat(tests): add worst case tests for PUSH opcodes

[LouisTsai-Csie]

🗒️ Description

This test case is designed to simulate the worst-case scenario for the PUSH operation in the EVM. It includes two approaches:

1. Repeatedly execute a PUSH-POP pattern to fill the contract code up to the maximum allowed size.
2. Deploy a contract that performs consecutive PUSH operations until the EVM stack reaches its maximum depth, then, deploy another contract that repeatedly performs STATICCALL to the first contract.

Based on the discussion in Berlinterop, and the analysis in PR #1737, we would only try the second approach

🔗 Related Issues

Issue #1687

✅ Checklist

• All: Set appropriate labels for the changes.
• All: Added an entry to CHANGELOG.md.
  with removal of converted JSON/YML blockchain 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.

[marioevz]

Just two minor comments and we can merge, thanks!

[LouisTsai-Csie]

@marioevz thanks for review, I would prefer this PR #1768 to be merged first before the second review. I want to replace the hardcoded stack limit with the fork configuration.

[marioevz]

#1768 is merged now, could you try rebasing and fix conflicts so we can merge pls?

[marioevz]

Needs a rebase since git merge seems to be confusing the PUSH and SWAP tests.

[LouisTsai-Csie]

I will wait for the PR #1767 to be merged, or I will need to rebase again.

[marioevz]

#1767 is now merged, we can rebase 👍