test(prisma-next): update negative factory assertions to new-convention names

Follow-up to the camelCase rename: the 'no *OrdOre / no string factory'
negative assertions checked old-convention names (encryptedBigIntOrdOre,
encryptedString) that never existed either way — pass, but off-convention.
Now check the new-convention names (bigIntOrdOre, textOrdOre, string).

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

Author: coderdan

packages/prisma-next/test/column-types.test.ts

@@ -113,11 +113,12 @@ describe('v3 TS factories', () => {
     })
   })
 
-  it('exposes no *OrdOre factories and no v3 encryptedString', () => {
+  it('exposes no *OrdOre factories and no v3 string factory', () => {
     const exported = columnTypes as Record<string, unknown>
-    expect(exported['encryptedBigIntOrdOre']).toBeUndefined()
-    expect(exported['encryptedTextOrdOre']).toBeUndefined()
-    expect(exported['encryptedString']).toBeUndefined()
+    expect(exported['bigIntOrdOre']).toBeUndefined()
+    expect(exported['textOrdOre']).toBeUndefined()
+    // v3 text uses `text`/`textEq`/`textSearch`/… — there is no `string`.
+    expect(exported['string']).toBeUndefined()
   })
 })