[feat]: Add Redis-Backed Job Queue for Verification Commands

This can only be picked after #7 has been completed

### Problem
Verification flows include waits and network-heavy work, which can block responsiveness under load.

### Proposed Work
- Introduce a Redis-backed queue (for example BullMQ) for `ccverify` and `cfverify` workflows.
- Move long-running verification steps to workers and provide status updates to users.
- Add retry policy and dead-letter handling for transient failures.

### Acceptance Criteria
- Verification jobs are processed asynchronously with clear user feedback.
- Failed jobs are retried with bounded attempts and logged with context.
- Worker and queue configuration are documented for local and production usage.

Wait for issue #7 to be completed, then inspect the `ccverify` and `cfverify` workflows and determine where long-running verification steps currently run. The work is done when those flows provide asynchronous status feedback, bounded retries and contextual logging for failed jobs, with worker and queue setup documented for local and production use.

Written by the indexing model from the issue text.