test(v10/e2e): Pull Supabase images from GHCR (#25719)

Backport of: #25718

## Differences to the original PR

- `supabase-nextjs/package.json`: v10 keeps its `supabase init` and
`supabase db reset` steps. `SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io` is
also set on `supabase db reset`, so the reset uses the same GHCR images
and does not pull from the default registry.

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 init --force --workdir . && supabase start -o env && supabase db reset",
+    "start-local-supabase": "supabase stop --no-backup 2>/dev/null || true && supabase init --force --workdir . && SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io supabase start -x postgres-meta -o env && SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io supabase db reset",
     "test:prod": "TEST_ENV=production playwright test",
     "test:build": "pnpm install && pnpm start-local-supabase && pnpm build",
     "test:assert": "pnpm test:prod"