fix(prisma-next): make the JSON encryptQuery cast suppressions effective

The `searchableJson` encryptQuery call spreads its two `as never` operands
across separate argument lines, so the single `// biome-ignore` above the call
reached neither cast — both still tripped the no-type-erasing-assertions plugin,
and the ignore itself was flagged as an ineffective suppression. Put one ignore
directly above each cast line. Warning-only (CI gates on errors), but resolves
the CodeRabbit thread and the dangling ineffective-suppression note. The scalar
branch was already correct.

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

Author: coderdan

packages/prisma-next/src/v3/sdk-adapter-v3.ts

@@ -244,10 +244,13 @@ export function createCipherstashV3Sdk(
       // this mirrors stack-drizzle's JSON containment usage exactly.
       await Promise.all(
         jsonTerms.map(async (slot) => {
-          // Cast rationale: see the scalar branch above.
-          // biome-ignore lint/plugin: deliberate bridge into the structural `never`-operand surface (rationale above)
+          // Cast rationale: see the scalar branch above. The two operands sit
+          // on separate argument lines, so each cast needs its own ignore —
+          // a single comment above the call reaches neither.
           const result = await client.encryptQuery(
+            // biome-ignore lint/plugin: deliberate bridge into the structural `never`-operand surface (rationale above)
             slot.plaintext as never,
+            // biome-ignore lint/plugin: deliberate bridge into the structural `never`-operand surface (rationale above)
             { table, column, queryType: 'searchableJson' } as never,
           )
           const term = unwrap(result, 'encryptQuery(searchableJson)')