[POC] Add filtering capabilities to SelectNext

[acelaya]

Part of #1254

This PR adds a new SelectNext.Filterable component, designed to wrap SelectNext.Options objects, and allow them to be filtered via text query.

Grabacion.de.pantalla.desde.2023-10-09.11-18-50.webm

Usage

Proposal was described in Part of #1254

TODO

• Currently changing the input content triggers a re-render, which makes every option call shouldRender as expected.
  However, this is not very obvious. There should be a more direct way to call shouldRender instead of relying on it being called as a side effect.
• Since Options are responsible for their own rendering, there's no easy way to tell if none are being rendered in order to display a "No results" placeholder.
• It might make sense to debounce the invokation to onFilter
• The original design includes a magnifying glass icon in the search box. We don't have one yet.
• We might want to customize the native "clear" button for input[type="search"]. Maybe using a text input with a custom clear button would be an option.

Testing steps

This can be tested in http://localhost:4001/input-select-next, with the Select with filtering example.

[acelaya]

Closing this for now. It can serve as an example if we decide to come back to it at some point.