feat(tests): extra stack operation test for CLZ opcode

[LouisTsai-Csie]

🗒️ Description

Hardening Fusaka for EIP-7939

Add two additional test cases for stack manipulation related to the CLZ (Count Leading Zeros) opcode:

1. No Stack Overflow
   The CLZ operation must never cause a stack overflow, as it does not increase the number of items on the stack.
   Test: Push 1022 items onto the stack, then execute CLZ 256 times while storing the result after each call. Ensure that no stack overflow occurs during this process.
2. Consistency Across Equivalent PUSH Operations
   For the same numeric value pushed onto the stack, the CLZ opcode should yield the same result, regardless of which PUSH variant (PUSH1 to PUSH32) was used.
   Examples:

• Pushing the value 0x01 using any PUSH1–PUSH32 should result in the same CLZ output.
• Pushing the value 0x0A000000 (10 00 00 00 in hex) using any PUSH4–PUSH32 should also produce a consistent result.

🔗 Related Issues or PRs

Issue #1795

✅ Checklist

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx --with=tox-uv tox -e lint,typecheck,spellcheck,markdownlint

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

[marioevz]

Looks good! Just a couple of comments, thanks!

[marioevz]

I feel we should use Op.CLZ(op[1 << bit]) to guarantee that the PUSHn opcode is the one that pushes to the stack right before CLZ.

[marioevz]

Could we cram all these into a single test? I feel this generates way too many tests.

[LouisTsai-Csie]

Yes, I put all the test cases into a single test, and remove the parametrization