404 page is shown when using on-demand revalidation with `dynamicParams=false` and `generateStaticParams` in production

### Link to the code that reproduces this issue https://github.com/better-salmon/404-after-on-demand-revalidation ### To Reproduce 1. Build and start the app with `npm run build && npm run start`. 2. Open http://localhost:3000/should-work in the browser. 3. Click either of the Revalidation buttons. ### Current vs. Expected behavior **Expected behavior:** The page is revalidated, and the new data is shown. **Actual behavior:** 404 page is shown after reloading. ### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.1.0: Mon Oct 9 21:28:31 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T8112 Binaries: Node: 20.9.0 npm: 10.1.0 Yarn: N/A pnpm: 8.10.0 Relevant Packages: next: 14.0.2-canary.18 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 ### Additional context _No response_