Resolve a theme token under dark: to its dark value

[sadiqk2]

The bug

dark:bg-theme-surface renders the light colour in dark mode.

A theme token resolves its own dark companion, so bg-theme-surface already returns ['bg' => light, 'dark' => ['bg' => dark]]. The dark: prefix then wrapped that entire result in a second dark layer:

TailwindParser::parse('dark:bg-theme-primary');
// was  ['dark' => ['bg' => '#FF6B00', 'dark' => ['bg' => '#FFA85C']]]
// now  ['dark' => ['bg' => '#FFA85C']]

parse() merges one dark level, so the buried companion is never lifted: the light hex ends up in the dark slot, and the nested dark key travels to the renderers as a prop they know nothing about.

The fix

Asking for a theme token under dark: can only mean that token's dark-mode form, so the companion is promoted instead of nested. A token whose resolver answers light-only keeps its single colour — the only sensible reading of the request, and the same thing the unprefixed form does.

The unprefixed path is untouched.

Verification

• Three tests added to tests/Unit/Edge/ThemeClassTokensTest.php: the dark-companion case, the light-only case, and the unprefixed shape staying exactly as it was.
• The first fails against main and passes with this change.
• vendor/bin/pest tests/Unit/Edge/: 276 passed. Full-suite failures match main's baseline (Android splash-screen and release-build tests, unrelated).
• vendor/bin/pint --test clean on both touched files.