test(webapp): give the NEW store its production schema variant

Production builds the NEW run-ops store with schemaVariant "dedicated", but
both hetero routing tests omitted it, so the store defaulted to "legacy". The
two variants take different read paths: findRun routes through the dedicated
relation-stripping adapter only when the variant is set, so the tests were
exercising the legacy path for a store that is dedicated in production.

Verified the branch is now reached by making the dedicated arm throw, which
failed 3 of the 5 tests.

Author: d-cs

apps/webapp/test/performTaskRunAlertsStoreRouting.test.ts

@@ -34,7 +34,11 @@ vi.setConfig({ testTimeout: 60_000 });
 // routed read, so each store uses its OWN prisma.
 
 function buildRoutingStore(prisma17: PrismaClient, prisma14: PrismaClient) {
-  const newStore = new PostgresRunStore({ prisma: prisma17, readOnlyPrisma: prisma17 });
+  const newStore = new PostgresRunStore({
+    prisma: prisma17,
+    readOnlyPrisma: prisma17,
+    schemaVariant: "dedicated",
+  });
   const legacyStore = new PostgresRunStore({ prisma: prisma14, readOnlyPrisma: prisma14 });
   return new RoutingRunStore({ new: newStore, legacy: legacyStore });
 }

apps/webapp/test/updateMetadataStoreRoutingHetero.test.ts

@@ -23,7 +23,11 @@ vi.setConfig({ testTimeout: 60_000 });
 // to NEW, a 25-char cuid to LEGACY.
 
 function buildRoutingStore(prisma17: PrismaClient, prisma14: PrismaClient) {
-  const newStore = new PostgresRunStore({ prisma: prisma17, readOnlyPrisma: prisma17 });
+  const newStore = new PostgresRunStore({
+    prisma: prisma17,
+    readOnlyPrisma: prisma17,
+    schemaVariant: "dedicated",
+  });
   const legacyStore = new PostgresRunStore({ prisma: prisma14, readOnlyPrisma: prisma14 });
   return new RoutingRunStore({ new: newStore, legacy: legacyStore });
 }