Pay Ops - enhance exception management process

### Goal:
Formalize how production errors are located, as well as how they are documented and resolved.

| Requirement | Minimal Implementation |
|:---------------------:|:--------------------------------:|
| Record of prod errors | Mandatory ticket per incident |
| Evidence of issue | Link to GCP logs / alerts |
| Action taken | Ticket fields + comments |
| Reviewer identified | Peer name + comment |
| Second‑person review | Ticket state + reviewer comment |
| Change before prod | Ticket must be reviewer‑approved |

### Ticket could capture:
Error reference: GCP log ID / incident URL / timestamp
Impact summary: What failed, who was impacted
Initial assessment: Root cause (or “unknown / under investigation”)
Action taken: Config change, code change, rollback, no‑change, etc.
Reviewer: Name + date of someone other than the implementer
Follow‑up: Log bug as a preventive action or “none required”