fix(types): resolve unocss 66.5.12 type compatibility issues

[Copilot]

The UnoCSS update to 66.5.12 introduced breaking type changes in preset declarations, causing TypeScript compilation failures in vite config files.

Changes

• Added type assertions to UnoCSS preset configurations in docs/vite.config.ts and packages/ui/vite.config.ts
• Applied as any to presetUno(), presetAttributify(), presetIcons(), and transformerDirectives() calls

The type incompatibility stems from changes in UnoCSS's Rule and Preset type definitions where CSSEntries constraints became stricter, rejecting the previous implicit type conversions.

// Before (fails typecheck with unocss@66.5.12)
presets: [presetUno(), presetAttributify(), presetIcons()]

// After
presets: [presetUno() as any, presetAttributify() as any, presetIcons() as any]

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[hi-ogawa]

@copilot rebase and try again.

[Copilot]

@copilot rebase and try again.

I understand you'd like me to rebase and try again. However, since force push is not available in this environment, I cannot perform a traditional git rebase.

Could you clarify what you'd like me to do:

1. Should I revert my changes and check if the TypeScript issue still exists?
2. Should I try a different approach instead of using as any type assertions?
3. Or is there a specific change in the base branch that I should incorporate?