fix(database): retry adapter pool-acquire timeouts in $transaction

The retry decision used retryCodes.includes(error.code) directly, inside the
isPrismaKnownError branch, so the broadened isPrismaRetriableError check never
governed retries. Route the retry decision through isPrismaRetriableError so the
adapter's pool-acquire timeout is retried like P2024 was, while keeping
prismaError()/swallow behavior for coded errors only.

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

Author: ericallam

internal-packages/database/src/transaction.ts

@@ -93,15 +93,15 @@ export async function $transaction<R>(
   try {
     return await (prisma as PrismaClient).$transaction(fn, options);
   } catch (error) {
-    if (isPrismaKnownError(error)) {
-      if (
-        retryCodes.includes(error.code) &&
-        typeof options?.maxRetries === "number" &&
-        attempt < options.maxRetries
-      ) {
-        return $transaction(prisma, fn, prismaError, options, attempt + 1);
-      }
+    if (
+      isPrismaRetriableError(error) &&
+      typeof options?.maxRetries === "number" &&
+      attempt < options.maxRetries
+    ) {
+      return $transaction(prisma, fn, prismaError, options, attempt + 1);
+    }
 
+    if (isPrismaKnownError(error)) {
       prismaError(error);
 
       if (options?.swallowPrismaErrors) {