refactor(gateway): keep admitted personal-profile requests running (#201083)

Problem: a personal GitHub request (`sessions.github.options`, status, polls) was refused mid-request with "Personal profile request connection is no longer current; reconnect and try again." whenever its WebSocket closed, and retained requests could be refused with "Gateway requester authority changed". 21 such refusals were logged on one host in four days.

Fix: personal-profile authority (profile, role/scope ceiling, credential owner) is checked once at admission and fixed for the request. A socket close, role edit or policy change applies to the next request. Explicit request cancellation, admitted-run cancellation, profile merge identity, credential generation and target fences still stop or refuse work. OAuth callbacks re-admit as a new start. The router's dispatch-scope check is unchanged.

User impact: a started GitHub read or publication finishes even if the dashboard disconnects or the role changes meanwhile; the next request reflects the change.

Proof: real Gateway from source: socket closed 3/5/10 ms after sending refuses with the exact logged error on base and finishes on head; closing before admission and a fresh request after real role revocation are refused on both. Regression and consumer tests cover cancellation, merge, generation and next-request refusal.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>