test(e2e): Pull Supabase images from GHCR (#25718)

## What

The `supabase-nextjs` E2E app now pulls the local Supabase images from
GHCR instead of the public AWS registry, and no longer starts
`postgres-meta`, which the test does not use.

## Why

Anonymous pulls from `public.ecr.aws` often fail on CI with
`toomanyrequests: Data limit exceeded`, because GitHub runners share the
per-IP quota with other projects.

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

Author: andreiborza

dev-packages/e2e-tests/test-applications/supabase-nextjs/package.json

@@ -7,7 +7,7 @@
     "build": "next build",
     "start": "next start",
     "clean": "npx rimraf node_modules pnpm-lock.yaml .next",
-    "start-local-supabase": "supabase stop --no-backup 2>/dev/null || true && supabase start -o env",
+    "start-local-supabase": "supabase stop --no-backup 2>/dev/null || true && SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io supabase start -x postgres-meta -o env",
     "test:prod": "TEST_ENV=production playwright test",
     "test:build": "pnpm install && pnpm start-local-supabase && pnpm build",
     "test:assert": "pnpm test:prod"