shadcn-ui/lint's stylesheet resolution for `package.json` `exports` subpath patterns.

### What happens

A CSS entry that imports a stylesheet from a dependency whose `package.json` exposes it through an `exports` subpath *pattern* (a key containing `*`) does not resolve. The Tailwind worker throws, the theme is never built, and the plugin prints one line on stderr:

```text
[@shadcn/lint] The Tailwind theme at src/app.css could not be built (@import "demo-widgets/styles.css" could not be resolved from /tmp/repro/src); no-unknown-classes is using the grammar bundled with @shadcn/lint there until it can.
```

Exit code stays 0. From then on `no-unknown-classes` judges every class against the bundled grammar, which knows nothing about the project `@theme`, so every utility the project declares is reported as unknown. The finding count scales with the size of the tree and all of it disappears the moment the `@import` resolves, so the failure reads as a rule problem rather than a resolution problem.

### Minimal reproduction

A fake dependency that ships its CSS behind a pattern export:

```jsonc
// node_modules/demo-widgets/package.json
{ "name": "demo-widgets", "version": "1.0.0", "exports": { "./*.css": "./dist/*.css" } }
```

```css
/* node_modules/demo-widgets/dist/styles.css */
.demo-widget { display: block; }
```

```css
/* src/app.css, the tailwind.css entry in components.json */
@import "tailwindcss";
@import "demo-widgets/styles.css";

@theme { --spacing-card: 1.25rem; }
```

```tsx
// src/page.tsx
export function Page() { return C...