Error boundaries ignored in Production with dynamicParams = true

[ackoppel-opus]

Link to the code that reproduces this issue

https://github.com/ackoppel/next-ssg-error-page

To Reproduce

1. npm run build
2. npm run start
3. open http://localhost:3000/bar/id -> Error.tsx reached
4. open http://localhost:3000/foo/id -> Raw Next 500 error page

Current vs. Expected behavior

Expected to reach error.tsx component while a runtime error ocurred.
Instead ended up with raw next 500 page.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Enterprise
  Available memory (MB): 65306
  Available CPU cores: 20
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  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)

Output (export/standalone)

Which stage(s) are affected? (Select all that apply)

next start (local)

Additional context

Have tested this with the following versions:
14.1.0
14.2.4

[ackoppel-opus]

similar issue #62046