test(nuxt): Pin the nuxt-5 e2e MongoDB image to 8.0 (#25564)

Same fix as #25557, applied to nuxt-5. It failed the same way on #25552
(`container e2e-tests-nuxt-5-mongo is unhealthy`)

The floating `mongo:8` tag moved to 8.3 on 2026-10-17. On CI the
container goes unhealthy some seconds after start. That is much earlier
than the healthcheck retries allow, so the server process exits, and
Docker then reports the container as unhealthy. If setup fails again,
the container logs now print, so we can see why mongod exits.

Author: s1gr1d

dev-packages/e2e-tests/test-applications/nuxt-5/docker-compose.yml

@@ -1,6 +1,7 @@
 services:
   mongo:
-    image: mongo:8
+    # `mongo:8` floats to the newest 8.x release, whose server sometimes exits right after start on CI.
+    image: mongo:8.0
     restart: always
     container_name: e2e-tests-nuxt-5-mongo
     ports:

dev-packages/e2e-tests/test-applications/nuxt-5/global-setup.mjs

@@ -7,8 +7,13 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 export default async function globalSetup() {
   // Start MongoDB via Docker Compose. `--wait` blocks until the
   // healthcheck in docker-compose.yml passes, so the app can connect immediately.
-  execSync('docker compose up -d --wait', {
-    cwd: __dirname,
-    stdio: 'inherit',
-  });
+  try {
+    execSync('docker compose up -d --wait', {
+      cwd: __dirname,
+      stdio: 'inherit',
+    });
+  } catch (error) {
+    execSync('docker compose logs --tail 50', { cwd: __dirname, stdio: 'inherit' });
+    throw error;
+  }
 }