test(nuxt): Pin the nuxt-4 e2e MongoDB image to 8.0 (#25557)

The nuxt-4 e2e jobs keep failing because the `mongo:8` container goes
unhealthy about 10s after it starts, fixed by pinning the image to
`mongo:8.0` and printing the container logs when setup fails so the next
failure shows why.

Author: logaretm

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

@@ -18,7 +18,8 @@ services:
       start_period: 10s
 
   mongo:
-    image: mongo:8
+    # `mongo:8` floats to the newest 8.x release, which keeps failing its healthcheck on CI.
+    image: mongo:8.0
     restart: always
     container_name: e2e-tests-nuxt-4-mongo
     ports:

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

@@ -7,8 +7,13 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 export default async function globalSetup() {
   // Start MySQL, MongoDB, and Redis via Docker Compose. `--wait` blocks until the
   // healthchecks in docker-compose.yml pass, 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;
+  }
 }