perf(webapp): match gate bypass list in pre-gate claim eligibility

debounce and oneTimeUseToken triggers always return pass_through from
the mollifier gate (`mollifierGate.server.ts:158-175`), so the pre-gate
claim was issuing an unnecessary Redis SETNX on the trigger hot path
for these trigger types. Mirror the gate's bypass list — exclude
debounce + oneTimeUseToken alongside the existing
resumeParentOnCompletion check — so the claim's RTT only fires when
the gate could actually mollify the request.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: d-cs

apps/webapp/app/runEngine/concerns/idempotencyKeys.server.ts

@@ -287,8 +287,16 @@ export class IdempotencyKeyConcern {
     // DB query, same predicate the gate uses — keeping the claim's Redis
     // RTT off the hot path for non-opted-in orgs during incremental
     // rollout.
+    // Match the gate's bypass list (`mollifierGate.server.ts:158-175`).
+    // debounce + oneTimeUseToken triggers always return pass_through from
+    // the gate, so claiming a Redis SETNX here is wasted RTT on the
+    // trigger hot path. Excluding them keeps the claim aligned with the
+    // gate — if the gate would never mollify the request, there's no
+    // buffer to serialise against.
     const claimEligible =
       !request.body.options?.resumeParentOnCompletion &&
+      !request.body.options?.debounce &&
+      !request.options?.oneTimeUseToken &&
       (await resolveOrgMollifierFlag({
         envId: request.environment.id,
         orgId: request.environment.organizationId,