useRouter replace/push works wrong with query-only navigation on mid-path dynamic routes

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/busy-hooks-nznk9l?workspaceId=ws_AYcZxx2mGgGyE3daYCqVTz ### To Reproduce 1. start codesandbox 2. click `Preview: 3000` 3. click `push to [a] page` → `/a/detail` 4. click `push to [b] page` → `/b/detail?fromId=a` 5. click `push to [c] page` → `/b/detail?id=c&fromId=b` ### Current vs. Expected behavior #### current 5. click `push to [c] page` → `/b/detail?id=c&fromId=b` #### expected 5. click `push to [c] page` → `/c/detail?fromId=b` ### Provide environment information ```bash Operating System: 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.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 15.5.5 // Latest available version is detected (15.5.5). eslint-config-next: N/A react: 19.0.0 react-dom: 19.0.0 typescript: 5.1.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Pages Router ### Which stage(s) are affected? (Select all that apply) next dev (local) ### Additional context Side effect of https://github.com/vercel/next.js/pull/82236 since https://github.com/vercel/next.js/releases/tag/v15.5.0 This bug occurs when a dynamic route is in the middle of a path (`e.g. /[id]/detail`) This bug does not occur when a dynamic route is at the end of a path (`e.g. /[id]`)