Intercepted routes don't update metadata

### Link to the code that reproduces this issue https://github.com/pseudotsuga-fir/nextgram-broken-metadata ### To Reproduce 1. Add unique metadata to an intercepted route ```js export async function generateMetadata({ params, }: { params: Promise<{ id: string }>; }): Promise<Metadata> { const id = (await params).id; return { title: `Page ${id} intercepted`, }; } ``` 2. Add link to a page that leads to intercepted route, see that intercepted page does not change the metadata ### Current vs. Expected behavior ## Current Metadata remains the same as the current page when intercepting a route, despite the intercepted route providing its own metadata. The metadata for the intercepted route WILL display however under the specific circumstance of navigating as such via the `<Link>` component: Page 1 (provides custom metadata) > Page 2 (does not provide metadata) > Intercepted Route (provides custom metadata). <img width="1399" alt="Screenshot 2024-11-18 at 2 49 26 PM" src="https://github.com/user-attachments/assets/08a61ce3-65bc-4eef-a910-e4beec432c0c"> ## Expected Metadata updates upon navigating to an intercepted route based on the metadata provided in the `page` of that route. <img width="1399" alt="Screenshot 2024-11-18 at 2 49 58 PM" src="https://github.com/user-attachments/assets/f1d9e3bf-476e-413b-8b89-08c464ea1950"> ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:06:26 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8112 Available memory (MB): 24576 Available CPU cores: 8 Binaries: Node: 20.18.0 npm: 10.8.2 Yarn: 1.22.22 pnpm: 8.9.0 Relevant Packages: next: 15.0.3 // Latest available version is detected (15.0.3). eslint-config-next: N/A react: 19.0.0-rc-fb9a90fa48-20240614 react-dom: 19.0.0-rc-fb9a90fa48-20240614 typescript: 5.6.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Metadata, P…