Cannot use a path named '/pages/[id]' with app router and edge runtime on Vercel. Next 14.04

### Link to the code that reproduces this issue https://github.com/Martoxdlol/next-on-vercel-error-pages-named-path-with-params ### To Reproduce 1. Deploy to vercel 2. Open `/pages/1` or /pages/any-other-param` on the production deployment on Vercel. ### Current vs. Expected behavior In dev mode it show the expected page under `/pages/[id]` (using any id, for example `/pages/1`). It is using the file with path `/app/pages/[id]/page.tsx`. In production mode locally does the same (it works as expected). If I access the same route on Vercel it throws a 500 internal server error. https://next-on-vercel-error-pages-named-path-with-params.vercel.app/pages/1 This happen only with edge runtime I think.  In the deployment summary it shows that it is not using the edge runtime when it should. Also it show the route `/[id]` wich doesn't really exist. If I try to access it, it throws a 404. On Vercel:  Local dev mode (using next dev):  Local production mode (using next build and next start):  ### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: win32 Arch: x64 Version: Windows 11 Pro Binaries: Node: 20.10.0 npm: N/A Yarn: N/A pnpm: 8.7.4 Relevant Packages: next: 14.0.5-canary.40 eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0 typescript: 5.1.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) App Router, Middleware / Edge (API routes, runtime) ### Which stage(s) are affected? (Select all that apply) Vercel (Depl…