redriveOutboundDlqMessages

Redrive selected dead-lettered messages back into the live stream. Operator endpoint — requires the integration:manage grant. A redriven message is re-enqueued at the tail with a new id and sequence — it is delivered out of its original per-entity order (the stream has moved on); this is inherent to redrive and matches SQS DLQ semantics. The redriven copy starts with zero delivery attempts and a fresh retention window; the original DLQ entry is removed. With reapply_mapping, the raw event is re-mapped with the use case's current jsonata_expression; entries whose mapping failed are always re-mapped. Per-id results report redriven, not_found (unknown ids, or entries concurrently redriven/expired) or mapping_failed (the re-mapping failed again and the entry stays in the DLQ).