Chore: upgrade libzkp v0.10.6

[lispc]

1. Purpose or design rationale of this PR

At the time between signer curie hardfork and ccc upgraded to v0.11, this PR will reject txs with BASEFEE/TLOAD/TSTORE/MCOPY with err msg like

assertion `left == right` failed left: None right: Some(InvalidOpcode(INVALID(92)))

to prevent any inconsistency between sequencer and ccc.

Details: original commit: scroll-tech/zkevm-circuits@aabc96b#diff-1e6d053f6514ddc64497b6a584b3543a639730560b44b5fdf47a2c6b58b2ecd7R1626
When ccc thinks an opcode is invalid, it will require l2geth also treat the opcode as invalid.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes