Wrong `error.tsx` matched using both parallel and dynamic routes

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/wonderful-dewdney-gp48mc

To Reproduce

1. Start the dev server and open the preview: Home error and Slot error are shown correcly.
2. Navigate to /page/one: two Home error are shown.

Current vs. Expected behavior

Current

1. Start the dev server and open the preview: Home error and Slot error are shown correcly.
2. Navigate to /page/one: two Home error are shown.

Expected

1. Start the dev server and open the preview: Home error and Slot error are shown correcly.
2. Navigate to /page/one: Home error and Slot error are shown correcly.

Provide environment information

Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.8 // Latest available version is detected (14.2.8).
  eslint-config-next: 14.2.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

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

Parallel & Intercepting Routes

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

next dev (local), next start (local)

Additional context

No response

Start with the linked CodeSandbox reproduction and inspect the parallel and intercepting route setup around /page/one. Run both next dev and next start, then compare the rendered Home and Slot errors before and after navigating to that route. Done means /page/one shows one Home error and one Slot error, matching the initial preview.