feat: notify miner to skip obviously large txns without executing them twice

[omerfirmak]

1. Purpose or design rationale of this PR

miner will skip a txn if it counter-based CCC says so, but there might be cases where counter-based CCC thinks a txn is OK but Rust CCC thinks otherwise.

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

[0xmountaintop]

so basically the workflow in this scenario is

counter-based ccc -> rust ccc -> shouldSkip -> reorg and add logic to directly skip this tx

?

[omerfirmak]

so basically the workflow in this scenario is

counter-based ccc -> rust ccc -> shouldSkip -> reorg and add logic to directly skip this tx

?

Yes, that is pretty much it. Should be fairly reliable in terms of catching skipped txns without causing too many reorgs.