next.js

2ca0d5df - [test] split `og-api` test suite into default and standalone variants (#93915)

[test] split `og-api` test suite into default and standalone variants (#93915) The fixture's `next.config.js` had `output: 'standalone'` hardcoded, which is meaningless on Vercel deployments (the standalone directory is ignored) but became a build-time crash after #93684 made the Turbopack NFT generator skip `next-server.js.nft.json` whenever an adapter is configured. With `output: 'standalone'` still active, `writeStandaloneDirectory` then fails with `ENOENT` when it tries to read that file ([x-ref](https://github.com/vercel/next.js/actions/runs/26006483168/job/76441905221)). This PR splits the `og-api` E2E suite into a default variant and a `standalone.test.ts` wrapper that enables `output: 'standalone'` via the `TEST_OUTPUT_STANDALONE` env var, and excludes the standalone wrapper from the deploy test manifest. The default variant still runs in `deploy` mode and preserves coverage of `next/og` from Pages Router API routes, App Router route handlers (edge and node), and middleware — paths not covered by the metadata-* fixtures. The standalone variant continues to exercise the trace-copy assertion in `next start` mode. --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl>