feat(infra): EventBridge/SNS task lifecycle event bus

**Context:** ROADMAP.md → EventBridge / SNS integration
**Related:** #228 (DLQ→SNS alarms only—not lifecycle events)

---

## Component

CDK / infrastructure

## Describe the feature

Publish **task lifecycle events** to **EventBridge** or **SNS** for external consumers beyond built-in DDB-Stream fanout (GitHub/Slack/email).

## Use case

Enterprises integrate ABCA with SIEM, internal workflow tools, or data warehouses. Fanout is channel-specific, not a general integration bus.

## Proposed solution

1. EventBridge bus + rules: `task.submitted`, `task.running`, `task.completed`, `task.failed`, `approval.required`, etc.
2. Optional SNS topic fan-out for simpler subscribers.
3. CDK opt-in; schema registry for event detail types.
4. IAM for cross-account publish (optional).
5. Document in `docs/design/API_CONTRACT.md` extension index.

## Other information

- Not the same as #228 (webhook processor DLQ alarms).
- Design context: `docs/design/OBSERVABILITY.md`, `docs/design/INPUT_GATEWAY.md`.

- [ ] This might be a breaking change

Inizia da ROADMAP.md e poi leggi docs/design/OBSERVABILITY.md, docs/design/INPUT_GATEWAY.md e docs/design/API_CONTRACT.md. L'issue non identifica gli entry point di CDK, i produttori di eventi, gli schemi, i test né una decisione tra EventBridge e SNS; questi confini e criteri di accettazione devono essere definiti prima che l'implementazione possa essere considerata completata.

Scritto dal modello di indicizzazione a partire dal testo della issue.