support-actions.ts stamps persona id instead of realUserId in actor/archive/log fields

audit-pluto-ca (Class-A follow-up found during PLUTO-643 pre-push review, PASS on 643 itself): three paths in support-actions.ts stamp the operating persona id instead of realUserId for actor/archive/telemetry attribution -- reporter submit (actor arg + failure log, user.id), admin create (actor arg + failure log, admin.id), and PLUTO-625 triage function (actor arg + failure log, admin.id). Active personas have isViewAs=false and realUserId!=id, so existing guards pass this through, but archive/telemetry attribution ends up wrong (persona row, not the real human). Fix: use realUserId for actor/archive/log fields at all three sites; retain the operating identity (user.id/admin.id) only for ticket OWNERSHIP fields, which should stay as-is. Add persona-shaped regression tests (isViewAs=false, realUserId!=id case) pinning the distinction. Class-A (touches attribution on an auth-adjacent surface), pre-push review applies. Do not widen PLUTO-643's scope for this -- separate WI/push.