fix(ci): approve esbuild/sharp builds via pnpm-workspace.yaml onlyBuiltDependencies

pnpm 10 moved build-script settings out of package.json (it now ignores the `pnpm` field) and treats esbuild's previously-ignored build as a hard ERR_PNPM_IGNORED_BUILDS in CI. Approve the builds in pnpm-workspace.yaml (the current settings home) and drop the no-longer-read package.json pnpm field.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Paul Mulligan

app/package.json

@@ -56,11 +56,5 @@
     "typescript": "^5.8.3",
     "vite": "^6.3.5",
     "vitest": "^3.2.4"
-  },
-  "pnpm": {
-    "onlyBuiltDependencies": [
-      "esbuild",
-      "sharp"
-    ]
   }
 }

app/pnpm-workspace.yaml

@@ -1,2 +1,5 @@
-ignoredBuiltDependencies:
+# pnpm settings live here (pnpm 10+). Approve build scripts so CI's
+# `pnpm install --frozen-lockfile` doesn't fail with ERR_PNPM_IGNORED_BUILDS.
+onlyBuiltDependencies:
   - esbuild
+  - sharp