fix(webapp): honor the caller's prisma client in the latest-deployment fallback

findCurrentWorkerDeployment resolved the caller-supplied client for the
promotion read but used the module-level client for the fallback read, so
callers passing a replica silently read the primary for that one query.

Author: ericallam

apps/webapp/app/v3/models/workerDeployment.server.ts

@@ -128,7 +128,7 @@ export async function findCurrentWorkerDeployment({
   }
 
   // We need to get the latest deployment of the given type
-  const latestDeployment = await prisma.workerDeployment.findFirst({
+  const latestDeployment = await $prisma.workerDeployment.findFirst({
     where: {
       environmentId,
       type,