fix(webapp): read run results from the owning store so triggerAndWait resolves for NEW runs

The run-result route built ApiRunResultPresenter with no run-ops read clients,
so under the split it read a NEW-residency run's row on the control-plane
database, found nothing, and returned 404. triggerAndWait and
runs.retrieve().result then never resolved for NEW runs, stalling the parent.
Wire the run-ops read clients the same way the batch-results route does.

Author: d-cs

apps/webapp/app/routes/api.v1.runs.$runParam.result.ts

@@ -2,6 +2,7 @@ import type { LoaderFunctionArgs } from "@remix-run/server-runtime";
 import { json } from "@remix-run/server-runtime";
 import { z } from "zod";
 import { ApiRunResultPresenter } from "~/presenters/v3/ApiRunResultPresenter.server";
+import { $replica, runOpsNewReplica, runOpsSplitReadEnabled } from "~/db.server";
 import { authenticateApiRequest } from "~/services/apiAuth.server";
 import { logger } from "~/services/logger.server";
 
@@ -27,7 +28,11 @@ export async function loader({ request, params }: LoaderFunctionArgs) {
   const { runParam } = parsed.data;
 
   try {
-    const presenter = new ApiRunResultPresenter();
+    const presenter = new ApiRunResultPresenter(undefined, undefined, {
+      newClient: runOpsNewReplica,
+      legacyReplica: $replica,
+      splitEnabled: runOpsSplitReadEnabled,
+    });
     const result = await presenter.call(runParam, authenticationResult.environment);
 
     if (!result) {