fix(components)!: consistent exposed refs

[benjamincanac]

🔗 Linked issue

Fixes #5380, follow-up on #5358

❓ 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

This PR standardizes exposed refs across components to always expose the underlying HTML element instead of the component instance.

⚠️ Breaking change on InputMenu, InputNumber, InputTags, Select, SelectMenu

const inputMenu = useTemplateRef('inputMenu')

- inputMenu.value.inputRef.$el // Component instance (ComboboxInput, etc.)
+ inputMenu.value.inputRef // HTML element (HTMLInputElement) directly

If you were accessing component-specific methods via inputRef.$el, update your code to use inputRef directly.

Other changes

• Internal refactoring: switched from ref() to useTemplateRef()
• Added missing "Expose" documentation sections for components with exposed refs

📝 Checklist

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

[benjamincanac]

@J-Michalek I ended up using toRef instead of a getter in defineExpose, it was easier to type the output.

[pkg-pr-new]

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

commit: 1ebda6f

[benjamincanac]

@J-Michalek I pushed another commit to consistently expose the actual html element.

I feel bad for introducing yet another breaking change but it didn't make sense to have inputRef as HTMLInputElement on Input.vue and as InstanceType<ComboboxInput> on InputMenu.vue 😬

What do you think?

[J-Michalek]

@benjamincanac Yeah exposing the same type for input based components makes sense!