test(prisma-next): guard the recorded bulk-decrypt call instead of unsafe ?.

Biome 2.5.3 (bumped in this group) adds lint/correctness/noUnsafeOptionalChaining,
which correctly flags `(call?.ciphertexts[0] as ...).c` — if `call` were
undefined the chain would throw anyway. Guard once and drop the optional
chaining; behaviour identical, and the lint gate stays green on the new
Biome. (The new version's extra useLiteralKeys/noNonNullAssertion findings
are warnings, which CI permits.)

Claude-Session: https://claude.ai/code/session_01MxTTPaPP16m6br7Hoab94w

Author: coderdan

packages/prisma-next/test/decrypt-all.test.ts

@@ -285,14 +285,15 @@ describe('decryptAll — one bulkDecrypt per routing-key group', () => {
 
     expect(sdk.bulkDecryptCalls).toHaveLength(1)
     const call = sdk.bulkDecryptCalls[0]
-    expect(call?.ciphertexts).toHaveLength(3)
+    if (!call) throw new Error('expected a recorded bulk decrypt call')
+    expect(call.ciphertexts).toHaveLength(3)
     // Order is the walker's discovery order — for a flat array this
     // is the array's own order; the assertion pins that the bulk
     // decrypt's `ciphertexts` slot lines up with the envelopes the
     // walker visits in sequence.
-    expect((call?.ciphertexts[0] as { c: string }).c).toBe('ct:x')
-    expect((call?.ciphertexts[1] as { c: string }).c).toBe('ct:y')
-    expect((call?.ciphertexts[2] as { c: string }).c).toBe('ct:z')
+    expect((call.ciphertexts[0] as { c: string }).c).toBe('ct:x')
+    expect((call.ciphertexts[1] as { c: string }).c).toBe('ct:y')
+    expect((call.ciphertexts[2] as { c: string }).c).toBe('ct:z')
   })
 
   it('groups by (sdk, routing key) so multi-tenant SDKs stay isolated', async () => {