feat: add more state_transition, worker, and tracing metrics

[georgehao]

1. Purpose or design rationale of this PR

getBlockTrace cost: 149ms
ccc applyTransaction: 295 ms
total cost : 4.5s

4500/(149+295+1) = 10

namely, commitTransactions parameter txs contains 10 tx, I think almost the real data. So if we can optimize this two function, the CommitTransactions performance will improved

Currently, the commitTransactions all cost at getBlockTrace and ccc applyTransaction.

This pr add metrics to investigate the cost of getBlockTrace

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

[HAOYUatHZ]

probably also need to bump version

[colinlyguo]

@HAOYUatHZ we found two small problems in the bump version bot: (i) will bump patch version in each commit without comparing the develop branch. (ii) unverified commit, thus stuck the CI.