feat(tests): add invalid p256verify cases

[LouisTsai-Csie]

🗒️ Description

Add invalid precompile input cases for p256verify precompile, it is one of the Nethermind gas-benchmarks cases.

🔗 Related Issues or PRs

Issue #2026

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

[LouisTsai-Csie]

A low hanging fruit for us to close issue #2026

[kclowes]

This LGTM! I left a comment about making the strings available via the spec file, but feel free to take or leave it :)

[kclowes]

Since we're now using these across test files, I wonder if we should assign them values within the Spec file and use them both here and in the test_p256verify.py. For example: Spec.H0_reversed or something?

[LouisTsai-Csie]

That's a good idea, but we are going to have a folder restructuring recently, i prefer to do it after that, and we could also update for different precompiles!