default.tsx parallel routes are using the loading.tsx from the parent route instead of the one from the parallel route

### Link to the code that reproduces this issue https://github.com/nuclei272/parallel-route-loading-ui-bug ### To Reproduce 1. Go to `https://codesandbox.io/p/github/nuclei272/parallel-route-loading-ui-bug/main`. 2. Click on the button to navigate to "/comments" route. 3. Click on the button to do a hard refresh. ### Current vs. Expected behavior When you click to hard refresh, you'll see that the header and sidebar parallel routes (`@header` and `@sidebar`) will incorrectly displays "Loading Children...", which is the loading.tsx on the parent route `/`. The children page displays the loading.tsx correctly and the route `/comments` is also displaying it correctly. The expected behaviour would be to loading the corresponding loading.tsx on `@header` and `@sidebar` parallel routes as seen when we first load the page on the root route `/`. ### Provide environment information ```bash Operating System: Platform: win64 Arch: x64 Version: Windows 11 Pro Available memory (MB): 15694 Available CPU cores: 4 Binaries: node: 21.2.0 yarn: 1.22.21 Relevant Packages: next: 14.3.0-canary.49 // Latest available version is detected (14.3.0-canary.49). eslint-config-next: 14.2.3 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) Parallel & Intercepting Routes ### Which stage(s) are affected? (Select all that apply) next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed) ### Additional context _No response_