fix(libzkp): upgrade to use prover v0.9.0

[silathdiir]

1. Purpose or design rationale of this PR

Upgrade to depend on zkevm-circuits/prover v0.9.0.
Could reference this notion for details.

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

[Thegaram]

Do we need to handle Error::InternalError("check rw failed") anywhere in the go code?

[0xmountaintop]

Do we need to handle Error::InternalError("check rw failed") anywhere in the go code?

OK I will handle in this PR

[0xmountaintop]

Do we need to handle Error::InternalError("check rw failed") anywhere in the go code?

Seems needing some efforts to handle it.

I think we can just print the error and let it be caught by grafana