feat(tests): add test for CLZ opcode with varying gas costs

[LouisTsai-Csie]

🗒️ Description

Add different gas cost test cases for CLZ opcode

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

[spencer-tb]

Thanks! Just some small changes. I wondered if it was worth combining this test with test_clz_gas initially, but happy to have this as its own case.

Could we also rename test_clz_gas to test_clz_gas_cost?

[LouisTsai-Csie]

Thanks! Just some small changes. I wondered if it was worth combining this test with test_clz_gas initially, but happy to have this as its own case.

I explored this idea before implementation, but based on my understanding, the CodeGasMeasure object is responsible for verifying the gas usage specified in its code field. Therefore, we can’t use it to test cases involving insufficient or excessive gas.

[spencer-tb]

Nice! LGTM :)

[spencer-tb]

Thanks for updating and the comment @jochem-brouwer!