feat: async ccc checker

1. Purpose or design rationale of this PR

this has been in testing for some time already, I want to merge it to develop and start deploying to internal follower nodes.

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
[x] 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

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
[x] Yes

Does this PR have the breaking-change label?