Changing search params on the same page does not reset the not found boundary

### Link to the code that reproduces this issue https://github.com/ali-idrizi/next-not-found-search-params-reproduction ### To Reproduce This is a very minimal reproduction. In the `/about` page if the `q` search param is `"404"`, then `notFound` is called. The layout has three buttons that call `router.push`, one to `/`, one to `/about` and the last to `/about?q=404`. Clicking the last button correctly shows the not found page. However, afterwards clicking `/about` no longer resets it. The 404 page goes away only after navigating to an entirely different page, or hard reloading. In the network tab, I can see that the request for RSC payload is being sent, and it does not contain the `NEXT_NOT_FOUND` error, but the client fails to update the content. https://github.com/user-attachments/assets/5e417703-8f70-4c35-9495-20e90318adbe ### Current vs. Expected behavior Once `notFound` has been called on `/about?q=404`, clicking the `/about` button should correctly render the page, but instead it keeps showing the not found error. ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023 Available memory (MB): 38098 Available CPU cores: 24 Binaries: Node: 20.10.0 npm: 10.2.3 Yarn: N/A pnpm: 8.15.1 Relevant Packages: next: 15.0.0-canary.139 // Latest available version is detected (15.0.0-canary.139). eslint-config-next: N/A react: 19.0.0-rc-fb9a90fa48-20240614 react-dom: 19.0.0-rc-fb9a90fa48-20240614 typescript: 5.5.4 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Navigation ### Which stage(s) are affected? (Select all that apply) next dev (local), next start (local) ### Additional context _No response_