Support `satisfies` for metadata and viewport exports in TypeScript IDE plugin

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/stupefied-drake-djhgvk?workspaceId=ws_FFy8WZFGHmk9xkeVqwsT43 ### To Reproduce 1. Create a [metadata export](https://nextjs.org/docs/app/api-reference/functions/generate-metadata#the-metadata-object) in a Next.js `page.tsx` or `layout.tsx` file, using the [`satisfies`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-9.html#the-satisfies-operator) keyword instead of directly setting the type: ```ts import { Metadata } from 'next' export const metadata = { title: 'My Website', } satisfies Metadata ``` 2. Enable the Next.js [TypeScript IDE plugin](https://nextjs.org/docs/app/api-reference/config/typescript#ide-plugin) 3. Notice that TypeScript emits the warning `The Next.js "metadata" export should be type of "Metadata" from "next".` despite the object being typed with the `satisfies` keyword. ### Current vs. Expected behavior I would expect the Next.js IDE plugin to detect the use of the `satisfies` operator and not emit a warning in this situation. ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 25.0.0: Mon Aug 25 21:17:51 PDT 2025; root:xnu-12377.1.9~3/RELEASE_ARM64_T6000 Available memory (MB): 16384 Available CPU cores: 10 Binaries: Node: 22.15.0 npm: 10.9.2 Yarn: N/A pnpm: 10.15.0 Relevant Packages: next: 15.5.2 eslint-config-next: N/A react: 19.1.1 react-dom: 19.1.1 typescript: 5.9.2 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) TypeScript ### Which stage(s) are affected? (Select all that apply) next dev (local) ### Additional context It's worth noting why it's important to support the `satisfies` operator here. We sometimes need to use the values for title, description, etc. in other places, and rather than define these in a 3rd object, we can directly import the metadata from routes. This en…