test(webapp): stub the task identifier cache in unit test setup

Stub the task identifier cache in webapp unit test setup so tests no
longer stall retrying an unavailable Redis before falling back to the
database.

Mono-RevId: 770ab4895119c6e1364c89b61159a997e0acc122

Author: pullfrog[bot]

apps/webapp/test/setup.ts

@@ -137,6 +137,15 @@ vi.mock("~/services/taskMetadataCacheInstance.server", async () => {
   return { taskMetadataCacheInstance: new NoopTaskMetadataCache() };
 });
 
+// getTaskIdentifiers() reads this cache before falling back to the database. The
+// defaulted REDIS_HOST above points it at a Redis CI doesn't run, so each read
+// stalls ~20 reconnect cycles (10s cold, ~40s warm) before its caught error.
+// Match the module's own behavior without a cache host: miss and fall through.
+vi.mock("~/services/taskIdentifierCache.server", () => ({
+  getTaskIdentifiersFromCache: vi.fn().mockResolvedValue(null),
+  populateTaskIdentifierCache: vi.fn().mockResolvedValue(undefined),
+}));
+
 // The org-data-stores registry singleton is constructed at import (transitively via
 // the ClickHouse factory instance, which many presenters pull in). Its ctor fires a
 // `forever` pRetry(loadFromDatabase) plus a setInterval reload against db.server's