ci(observer): fix ERESOLVE in dashboard deploy from wrangler peer bump (#245)

The deploy step runs `npx @cloudflare/next-on-pages@1`, whose ephemeral
install resolves the latest wrangler (4.108.0). That wrangler now peers on
@cloudflare/workers-types@^5, while next-on-pages peers on ^4, so npm aborts
the tree with ERESOLVE and the deploy fails.

Pin next-on-pages to 1.13.16 and set NPM_CONFIG_LEGACY_PEER_DEPS so the
optional-peer mismatch no longer blocks the install.


Claude-Session: https://claude.ai/code/session_01DatJJXxGLYDdgTWzT9zncq

Co-authored-by: Claude <noreply@anthropic.com>

Author: willwashburn

.github/actions/deploy-observer-dashboard/action.yml

@@ -58,8 +58,12 @@ runs:
       run: |
         set -euo pipefail
         cd packages/observer-dashboard
-        npx @cloudflare/next-on-pages@1
+        npx @cloudflare/next-on-pages@1.13.16
         npx wrangler pages deploy .vercel/output/static --project-name="${{ inputs.project-name }}" --branch="${{ inputs.branch }}"
       env:
         CLOUDFLARE_API_TOKEN: ${{ inputs.cloudflare-api-token }}
         CLOUDFLARE_ACCOUNT_ID: ${{ inputs.cloudflare-account-id }}
+        # next-on-pages peers on @cloudflare/workers-types@^4, but the wrangler it
+        # transitively resolves now peers on ^5; tolerate that optional-peer mismatch
+        # so the ephemeral npx install can resolve. See CI ERESOLVE on wrangler 4.108.0.
+        NPM_CONFIG_LEGACY_PEER_DEPS: "true"