refactor(gateway): check forwarded node approvals once at sanitization (#201947)

Problem: node.invoke re-checked a forwarded approval's liveness several times after the approval had been accepted: in the policy liveness callback, just before the raw transport after policy awaits, and in the registry's final isDispatchAuthorized. If the approval's retained binding changed while the command was being prepared, a node command that had already started was refused with "approved runtime authority closed before node dispatch".

Fix: a forwarded approval is checked once, when the request starts, by the forwarded-approval sanitizer (decision start check, provenance, target node, requester, command binding, allow-once consumption). isForwardedNodeInvokeApprovalAuthorityActive and resolveNodeInvokeRuntimeAuthorityError and their node.invoke uses are deleted. The sanitizer, allow-once consumption, retainForHandoff and the upload gate are unchanged; node.invoke still passes the upload gate to the policy's final send.

User impact: a node command whose forwarded approval was accepted is no longer refused because the approval's retained binding changed while the command was being prepared. A request whose approval is no longer usable is still refused at sanitization.

Proof: 12 node-dispatch test files (238 tests) on current main; tsgo and test types; oxlint, format and the lifetime-check, line-cap, session-identity, mock-export and max-lines ratchets; ocx build --dts plus a packed install smoke on the head.

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