fix(vuetify): separate composable auto-imports from component resolution

[BatLeDev]

Summary

• autoImports in lib-vuetify/vite.ts previously mixed composables (from lib-vue) with .vue component default exports. This was a bug: unplugin-auto-import only handles <script>-level imports, not template component resolution. The .vue entries had no effect and caused Vite "Cannot optimize dependency" warnings since esbuild cannot pre-bundle .vue files.
• autoImports now re-exports lib-vue composables only. Backwards-compatible: existing consumers importing autoImports from lib-vuetify keep working unchanged — they get the same composables as before, without the broken .vue entries.
• New componentsResolver for unplugin-vue-components: properly resolves Df-prefixed components (e.g. <DfPersonalMenu> or <df-personal-menu>) to their @data-fair/lib-vuetify/*.vue modules.
• Added TSDoc with usage examples on autoImports (in both lib-vue and lib-vuetify) and componentsResolver.

Migration

To enable component auto-resolution, add the resolver:

import { componentsResolver } from '@data-fair/lib-vuetify/vite.js'
import Components from 'unplugin-vue-components/vite'

Components({ resolvers: [componentsResolver] })

Test plan

• Tested in portals/ui with <df-personal-menu> without manual import — component resolves correctly
• "Cannot optimize dependency" warnings for .vue files are gone