fix(webapp): gracefully handle RegionsPresenter failure in bulk action loader

Wrap RegionsPresenter.call() with tryCatch so a failure (e.g. missing
defaultWorkerInstanceGroupId feature flag on self-hosted) falls back to
an empty regions array instead of breaking the entire bulk-action
inspector — including the cancel flow which has no dependency on regions.

Author: ericallam

apps/webapp/app/routes/resources.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs.bulkaction.tsx

@@ -91,20 +91,25 @@ export const loader = dashboardLoader(
         environmentId: environment.id,
         request,
       }),
-      new RegionsPresenter().call({
-        userId: user.id,
-        projectSlug: projectParam,
-        isAdmin: user.admin || user.isImpersonating,
-      }),
+      tryCatch(
+        new RegionsPresenter().call({
+          userId: user.id,
+          projectSlug: projectParam,
+          isAdmin: user.admin || user.isImpersonating,
+        })
+      ),
     ]);
 
+    const [regionsError, regionsData] = regionsResult;
+    const regions = regionsError ? [] : regionsData.regions;
+
     // Display flag for the inspector's Cancel/Replay controls — the action
     // below enforces write:runs independently.
     const { canCreateBulkAction } = checkPermissions(ability, {
       canCreateBulkAction: { action: "write", resource: { type: "runs" } },
     });
 
-    return typedjson({ ...data, regions: regionsResult.regions, canCreateBulkAction });
+    return typedjson({ ...data, regions, canCreateBulkAction });
   }
 );