[BUG] Keyboard input on InputChip misbehaving

[jameslounds]

Current Behavior

At the moment, the hidden select is focusable from the keyboard.

This leads to unexpected behaviours as select elements do have keyboard inputs, but they don't seem to work cross-browser.

Steps To Reproduce

1. Go to the InputChip docs page
2. Use inspect element to remove the h-0 overflow-hidden classes from the select element (helps to visually see what's going on)
3. Enter some items into the input chip, then shift + tab to focus the select
4. Use Arrow Keys, Control + Arrow Keys to navigate through select to see unintended behaviour

Anything else?

It would be useful to have some way to focus and remove chips using the keyboard.
Perhaps buttons instead of clickable spans would be better for the chips?

[jameslounds]

Having played around a little with the source code, it does seem to be as simple as just renaming the span to a button, adding some focus classes, and setting the tabindex on the select.

I could have.a PR ready basically whenever, but I'm not sure the best way to implement the focus styles - should they be in the same prop as the other chip styles? Should it be its own prop? Or perhaps on the tailwind side?