next: rename Listbox to Select and drop old select

[huntabyte]

Select and Listbox are way too similar to be separate components. This just creates confusion, and IMO, the original implementation of Listbox is much better.

This PR replaces the entire Select implementation with the current Listbox implementation + a few additional features to handle typeahead when the trigger is focused, and the content is closed via the items prop. We've dropped the Listbox component (if you were using it before, just replace Listbox with Select and the API is the same. If you were using the Select, you'll just need to make a few minor changes to get back up and running.

Now, users don't need to use an entirely different component/API for "multi-select"; the updated Select is capable of both.

Additionally, support has been added for auto-filling responses via password managers or otherwise, if you provide the items prop and it's a type="single" Select.

Closes #753
Closes #748

[changeset-bot]

🦋 Changeset detected

Latest commit: 6b7c78c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
bits-ui	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
bits-ui	✅ Ready (View Log)	Visit Preview	6b7c78c

[tomasz13nocon]

Hey, since Select can now have type="multiple" which changes value type to string[], how would one go about doing a reusable Select component with proper types, while passing the bind:value down to bits-ui?