Repository: next.js
Issue: `NextRscErrClientMetadataExport` thrown when mixing metadata and virtual css modules
Labels: bug,SWC

### Link to the code that reproduces this issue

https://github.com/jantimon/reproduction-next-server-component-css-error

### To Reproduce

1. clone https://github.com/jantimon/reproduction-next-server-component-css-error
2. npm install
3. npm run dev

### Current vs. Expected behavior

I am using a virtual css module (`./page.yak.module.css!=!./page?./page.yak.module.css`).

It looks like that this virtual css module is compiled by SWC and fails because it was marked as client component.

```
yarn dev
yarn run v1.22.19
$ next dev
  ▲ Next.js 14.2.4
  - Local:        http://localhost:3000

 ✓ Starting...
 ✓ Ready in 1491ms
 ⨯ ./src/app/page.tsx?./page.yak.module.css
Error: 
  × You are attempting to export "metadata" from a component marked with "use client", which is disallowed. Either remove the export, or the "use client" directive. Read more: https://nextjs.org/
  │ docs/getting-started/react-essentials#the-use-client-directive
  │ 
  │ 
   ╭─[/Users/jannicklas/Desktop/repo-yak-meta-data/src/app/page.tsx:2:1]
 2 │ import { Button } from "./button";
 3 │ import { styled } from "next-yak";
 4 │ import __styleYak from "./page.yak.module.css!=!./page?./page.yak.module.css";
 5 │ export const metadata: Metadata = {
   ·              ────────
 6 │   title: '...'
 7 │ };
 8 │ const Title =
   ╰────

Import trace for requested module:
./src/app/page.tsx?./page.yak.module.css
```

I would expect that SWC does not transpile this file at all

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.15.7
Relevant Packages:
  next: 15.0.0-canary.59 // Latest available version is detected (15.0.0-canary.59).
  eslint-config-next: N/A
  react: 19.0.0-rc.0
  react-dom: 19.0.0-rc.0
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

SWC

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

In the reproduction repository are two React Server components:

`page.tsx`:

```tsx
import { Metadata } from "next";
import { Button } from "./button";
import { styled } from "next-yak";

export const metadata: Metadata = {
  title: '...',
}

const Title = styled.h1`
  color: blue;
`;

export default function Home() {
  return (<>
    <Title>Hello</Title>
    <Button>Click me</Button>
  </>);
}
```

and `button.tsx`:
```tsx
import { styled } from "next-yak";

export const Button = styled.button`
  color: red;
`
```

The bug happens only if `export const metadata` and a yak styled component are in the same file.

Removing `export const metadata` or `Title` will not trigger the error.

This is surprising as the button is also a yak styled component and can be imported into a server component which uses `export const metadata`.