fix(mollifier): mock db.server in gate test to avoid eager prisma connect

The unit cascade tests in mollifierGate.test.ts import the gate module,
which transitively pulls in ~/db.server. That module constructs the
prisma singleton at import time and eagerly calls $connect(), which
fails against localhost:5432 in the unit-test shard and surfaces as an
unhandled rejection that fails the whole vitest run. Mocking the module
keeps the cascade tests pure and leaves the postgresTest cases on the
testcontainer-fixture prisma untouched.

Author: d-cs

apps/webapp/test/mollifierGate.test.ts

@@ -1,5 +1,17 @@
+import { describe, expect, it, vi } from "vitest";
+
+// Stub `~/db.server` before importing anything that transitively imports it.
+// The real module eagerly calls `prisma.$connect()` at singleton construction
+// (db.server.ts), so loading it under vitest tries to reach localhost:5432
+// and surfaces as an unhandled rejection that fails the whole shard — even
+// though no test in this file actually uses the default prisma client.
+// `postgresTest` provides its own container-backed prisma via the fixture.
+vi.mock("~/db.server", () => ({
+  prisma: {},
+  $replica: {},
+}));
+
 import { postgresTest } from "@internal/testcontainers";
-import { describe, expect, it } from "vitest";
 import { FEATURE_FLAG } from "~/v3/featureFlags";
 import { makeFlag } from "~/v3/featureFlags.server";
 import {