fix(types): allow arbitrary keys in tv config

[J-Michalek]

🔗 Linked issue

Resolves #4888

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I've loosened the types around tailwind variants to allow arbitary keys to be passed in as before TS would report an error for custom variants/slots being used in other block of the config.

Ideally we would have this fully typed, but as I discussed with @benjamincanac we cannot do that as of now due to some technical limitations.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[J-Michalek]

I still need to address the issue I've described in #4888 (comment) because if a component has no compoundVariants out of the box the user won't get any type support, but they should get atleast the slots/variants predefined by NuxtUI.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@4992

commit: b3b9007

[J-Michalek]

So I was able to solve #4992 (comment) pretty easily, but I am still strugling with allowing any value to be passed as the value of the variant (i.e. custom color) as any attempt of remapping the keys of the variants resulted in loss of typing of the original values.

[J-Michalek]

@benjamincanac I've used the type you've shared with me and it works great!

One thing that comes to mind, but in my opinion is not a blocker is that it would be nice to still restrict boolean variants to just boolean because now we allow string to be passed in as well.