test(deployments): pin staging's active-resume tests to the current generation

Two tests that staging added alongside durable PostHog delivery drive the
`operation.status === 'active'` resume branch this PR now gates, and neither
overrides `mockIsDeploymentOperationCurrent` — the suite's `beforeEach`
defaults it to `false`. Under the new gate they read as superseded, so the
handler short-circuits: the delivery test sees a resolve where it asserts a
rejection, and the unconsumed workflow row leaks into the next test.

Both are still-current resumes by intent, so they say so explicitly. The
checkpoints, not the generation gate, remain what keeps analytics from being
captured twice.

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

Author: icecrasher321

apps/sim/lib/workflows/deployment-outbox.test.ts

@@ -317,6 +317,12 @@ describe('versioned deployment preparation outbox', () => {
       mockActivateDeploymentOperation.mock.invocationCallOrder[0]
     )
 
+    /**
+     * The resume still owns the latest generation, so it re-enters
+     * post-activation work and the checkpoints — not the generation gate —
+     * are what must keep analytics from being captured twice.
+     */
+    mockIsDeploymentOperationCurrent.mockResolvedValue(true)
     mockGetDeploymentOperation.mockResolvedValue(active)
     queueTableRows(schemaMock.workflow, [
       { id: 'workflow-1', name: 'Workflow', workspaceId: 'workspace-1' },
@@ -349,6 +355,7 @@ describe('versioned deployment preparation outbox', () => {
   })
 
   it('does not checkpoint analytics until durable PostHog delivery resolves', async () => {
+    mockIsDeploymentOperationCurrent.mockResolvedValue(true)
     const active = operation({ status: 'active', completedAt: NOW })
     mockGetDeploymentOperation.mockResolvedValue(active)
     queueTableRows(schemaMock.workflow, [