Rebuild on Prisma Next

[SerhiyGreench]

What does this PR do?

Rebuilds this package on Prisma Next (8.x). Prisma 8 replaces the generated
client with a contract and drops $extends, so the four query extensions
become SqlMiddleware that rewrite a query AST, and everything they used to
read from the generated config maps (SOFT_DELETE_MODELS, AUDIT_CONFIG,
ACCESS_SCOPE_MODELS, …) is now derived from the emitted contract.json.

The Prisma 7 generator is gone with the client that hosted it. emit/ produces
the same decorated @imqueue/rpc classes from the contract, and carries the
three things a contract cannot: validation rules, fields kept off the wire, and
the names of enum members whose database label is not the name (STRING @map("string") had no equivalent, and losing it renamed a published field).

What the ORM cannot do, and what stands in for it:

Gone	Replacement
Nested writes	repositoriesFor writes the children itself, in a transaction, taking the foreign key from the row it just created
select on a write	A write returned every column — including a credential secret the caller had not asked for. The façade projects it, reading the row back when the projection names a relation
Atomic update values	A function passed as one is silently stringified, so a counter has to be x + 1 in the database
groupBy, createMany, skipDuplicates	createBulk, count, and conflictOn on upsert; the aggregate cases stay one statement rather than a loop

Three decoding bugs this fixes, each of which was silent:

• pg hands the codec an already-parsed JSON value and the codec parses it
  again. An object survived; a JSON string did not — and a column holding
  "5" came back as the number 5.
• An enum's array type is numbered when the enum is created, so the driver has
  no parser for it and returns the literal text {EMAIL,SMS}. Every read of
  such a column failed with RUNTIME.DECODE_FAILED.
• Both are corrected by dataPool, which gives the codec the text it expects
  and looks the enum-array oids up once.

isoDates stays, for a different reason than before. The columns are
timestamptz now, so the instant is no longer ambiguous — but Postgres prints
it as 2026-08-14 09:30:00.123+00, and every boundary downstream refuses that
spelling: the GraphQL DateTime scalar rejects it outright, and so does
z.iso.datetime().

Also new: sqlRunner (a query and a transaction that agree on the
connection, carried in async context so a statement written inside one is in
it), composable sql/raw/join fragments to replace Prisma.sql, and
RowOf<Model> with a Repository<Entity> that lets a call site read a row
without naming its type.

Validated by migrating seven services onto it, all green.

Type of change

• Bug fix
• New feature
• Documentation
• Refactor / internal
• Other: breaking — rebuilt for Prisma Next; the peer moves from
  @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8 and the
  ./codegen export is removed

Checklist

• I have read the Contributing guide.
• Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
• Docs / doc-blocks updated where relevant.
• The PR is focused on a single logical change.

Contribution terms (required)

• I have read and agree to the @imqueue Contribution Terms.
  I grant the project owner the right to license my contribution
  commercially, royalty-free, my contribution stays available under
  GPL-3.0, I keep my copyright, and I understand I will receive no fee for
  it. If I did not agree, I would not be submitting this contribution.