fix(webapp): route historical V1 cancel writes through the legacy run-ops handle

CancelTaskRunService.callV1 finalizes historical (engine V1) runs, which are
legacy-resident. It wrote them through the control-plane client, which misses
the row once legacy run-ops data lives on its own database. Route those two
writes through runOpsLegacyPrisma, matching every other legacy run-graph write.

Author: d-cs

apps/webapp/app/v3/services/cancelTaskRun.server.ts

@@ -1,4 +1,5 @@
 import { RunEngineVersion, type TaskRun } from "@trigger.dev/database";
+import { runOpsLegacyPrisma } from "~/db.server";
 import { engine } from "../runEngine.server";
 import { isCancellableRunStatus } from "../taskStatus";
 import { BaseService } from "./baseService.server";
@@ -43,15 +44,17 @@ export class CancelTaskRunService extends BaseService {
     // DB row directly. Never throw here: the cancel route returns 500 on any throw.
     if (!isCancellableRunStatus(taskRun.status)) {
       if (options?.bulkActionId) {
-        await this._prisma.taskRun.update({
+        // runops-legacy-ok: bulk-action tag on a historical V1 run (legacy-resident)
+        await runOpsLegacyPrisma.taskRun.update({
           where: { id: taskRun.id },
           data: { bulkActionGroupIds: { push: options.bulkActionId } },
         });
       }
       return { id: taskRun.id, alreadyFinished: true };
     }
 
-    await this._prisma.taskRun.update({
+    // runops-legacy-ok: finalize (cancel) a historical V1 run (legacy-resident)
+    await runOpsLegacyPrisma.taskRun.update({
       where: { id: taskRun.id },
       data: {
         status: "CANCELED",