feat(orchestration): orchestrator DLQ and replay

**Context:** ROADMAP.md → Orchestrator DLQ

---

## Component

API or orchestration

## Describe the feature

**Dead-letter path** for task orchestration after durable execution retry exhaustion. Operators inspect and **replay** failed orchestration runs.

## Use case

Transient AWS faults or code bugs can exhaust durable retries with no durable artifact for ops. Webhook processor has DLQ (#284); orchestrator does not.

## Proposed solution

1. Configure DLQ on durable orchestrator Lambda (SQS).
2. Payload: task_id, checkpoint, error, timestamp.
3. CloudWatch alarm on DLQ depth (#117 pattern).
4. Operator API/CLI: list DLQ messages, replay with idempotency guard.
5. Document runbook in `docs/design/ORCHESTRATOR.md`.

## Other information

- Distinct from FanOutConsumer DLQ (#117).
- Design context: `docs/design/ORCHESTRATOR.md`.

- [ ] This might be a breaking change

Inizia da ROADMAP.md e docs/design/ORCHESTRATOR.md, quindi confronta la DLQ del processore webhook in #284 con il pattern di allarme CloudWatch in #117. Definisci la DLQ, il payload, l'allarme, il flusso di elenco e replay dell'API/CLI dell'operatore, la protezione dall'idempotenza e il runbook; il lavoro è completato quando questi elementi sono implementati e documentati.

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