Catch-all route also intercepts and catches static assets and js chunks

### Link to the code that reproduces this issue https://github.com/r6203/next-catch-all-bug ### To Reproduce 1. Create a catch-all route 2. run `next dev` 3. go to any static route or js chunk or view server logs to see chunks intercepted ### Current vs. Expected behavior Having a catch all route at the root of the app shouldn't intercept next generated assets or static assets. Expect a working app where each non asset request resolves to the catch-all route but requests to next generated assets (_next/**/*) to resolve to the corresponding files. ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 Available memory (MB): 60075 Available CPU cores: 16 Binaries: Node: 22.2.0 npm: 10.7.0 Yarn: N/A pnpm: 9.9.0 Relevant Packages: next: 14.2.12 // An outdated version detected (latest is 15.0.3), upgrade is highly recommended! eslint-config-next: N/A react: 18.3.1 react-dom: 18.3.1 typescript: 5.4.5 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Navigation, Runtime ### Which stage(s) are affected? (Select all that apply) next dev (local), next start (local) ### Additional context For an in-production example of this issue with a workaround see https://github.com/session-foundation/websites/tree/main/apps/foundation Note this is reopening this issue https://github.com/vercel/next.js/issues/67806