Escalate Cs Ticket

Rooster's escalation tool (see app/modules/rooster/escalation.py): he lacks the information, the authority, or a tool to answer this ticket himself, and is saying so rather than guessing. Records a 'proper_escalation' disposition -- docs/SUPERVISION_DESK.md: a SUCCESS, not a failure -- and raises a human-visible ActionItem routed the same way every other ticket-scoped card in this codebase already is (app/modules/customer_service/ticket_routing.py): the ticket's own assignee, else (b2g) the agency's account manager, else a visible pool. Never an account manager seeing a consumer ticket or vice versa.

Gated on the SAME rooster:cs:draft grant as every other CS-drafting route -- deciding he cannot draft this one himself is part of the same drafting capability, not a new one. Idempotent per ticket: a repeat call while an escalation for this ticket is still on file reuses that card and records no second disposition (created: false).