outputFileTracing increases export build time by 1.5-2x

### Link to the code that reproduces this issue https://github.com/lnewson/nextjs-reproduction ### To Reproduce 1. Run `yarn build` and take note of the time (~5s for me) 2. Edit `next.config.ts` and change `outputFileTracing` to `true` (or just delete it) 3. Run `yarn build` and take note of the time (~8s for me) 4. Attempt to exclude all files from being traced by adding the following and run `yarn build`, but note it makes little to no difference. ``` experimental: { outputFileTracingExcludes: { '**/*': ['./**/*'], }, }, ``` ### Current vs. Expected behavior We've not long upgraded to Next.js 14 and logging this issue per the following warning added in Next.js 14: > ⚠ Disabling outputFileTracing will not be an option in the next major version. Please report any issues you may be experiencing to https://github.com/vercel/next.js/issues The expected behaviour would be that the file tracing can either be disabled still or that having it enabled does not drastically reduce export build performance. Ideally for export builds, as I cannot see a reason for it in that case, it would be good if it didn't run at all. ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 Available memory (MB): 65536 Available CPU cores: 10 Binaries: Node: 20.11.1 npm: 10.2.4 Yarn: 1.22.19 pnpm: N/A Relevant Packages: next: 14.2.3 // Latest available version is detected (14.2.3). eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0 typescript: 5.4.3 Next.js Config: output: export ``` ### Which area(s) are affected? (Select all that apply) Performance, Upstream ### Which stage(s) are affected? (Select all that apply) next build (local) ### Additional context For our use case we are just using Next.js as a static site generator and then hosting the generated output using a webserver. So having th…