revert(webapp): drop the in-list padding extension

Padding was applied to the whole Prisma args object, so it rewrote values as
well as predicates: a write payload or JSON comparison value containing a field
named in or notIn had its trailing element duplicated. Bounding list arity is
better handled per call site, where filter context is unambiguous.

Author: ericallam

.server-changes/pad-prisma-in-list-filters.md

@@ -30,7 +30,6 @@ import { DATASOURCE_CONTEXT_KEY, startActiveSpan } from "./v3/tracer.server";
 import type { Span } from "@opentelemetry/api";
 import { context, trace } from "@opentelemetry/api";
 import { queryPerformanceMonitor } from "./utils/queryPerformanceMonitor.server";
-import { padInLists } from "./utils/padInLists.server";
 
 export type {
   PrismaTransactionClient,
@@ -132,7 +131,7 @@ function tagDatasource<T extends PrismaClient>(datasource: "writer" | "replica",
         trace.getActiveSpan()?.setAttribute("db.datasource", datasource);
         return context.with(
           context.active().setValue(DATASOURCE_CONTEXT_KEY, datasource),
-          async () => await query(padInLists(args))
+          async () => await query(args)
         );
       },
     },
@@ -152,7 +151,7 @@ function tagDatasourceRunOps(
         trace.getActiveSpan()?.setAttribute("db.datasource", datasource);
         return context.with(
           context.active().setValue(DATASOURCE_CONTEXT_KEY, datasource),
-          async () => await query(padInLists(args))
+          async () => await query(args)
         );
       },
     },