Support-ticket API parity - create/triage/status ops + list read, no UI-only actions

Fleet directive (Elazar via pmmaster-evolutiva-cc): every support-ticket action a human can do in /admin/soporte must be agent-operable via API. Audit found 3 UI-only actions (adminCreateSupportTicket, updateSupportTicketTriage, arbitrary updateSupportTicketStatus) plus no list/discovery read - GET required a ticketId that no API handed out. Closed by adding create/triage/status ops and a GET list mode to /api/internal/support-action, each delegating to the same shared core the browser action calls, plus a mutation-checked coverage test asserting no operator-page server action lacks a bearer op.