chore(libzkp): upgrade to v0.9.13, support next hard fork transition

[lispc]

1. Purpose or design rationale of this PR

...

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

[colinlyguo]

So we can merge this PR instead of #691?
looks like there will be a 0.10.x upgrade next.

[HAOYUatHZ]

conclusion:

1. v0.9.13 will not reject "sha256 treated as invalid op" (same behavior before hard fork)
2. v0.9.13 will reject "sha256 treated as valid op" (dropped from txpool) (valid tx after hard fork but we drop it temporarily)
3. then we upgrade to v0.10.0 after the fork
4. both this PR and feat(libzkp): ccc v0.10.2 (enable sha256, remove StructLog.stack) #691 's c1fc87d are related to sha-256 but fix different things. this PR fixes the transition, feat(libzkp): ccc v0.10.2 (enable sha256, remove StructLog.stack) #691 fixes the overestimation and in feat(libzkp): ccc v0.10.2 (enable sha256, remove StructLog.stack) #691 we need to upgrade the circuits