feat(web-awesome): add search to Tags filter dropdown - #840

First contribution — please approve workflows when you have a moment.

@epszaw Can you please take a look or direct me on whats needed to get this one merged, this should be a simple one.
Thank you
MJ

Thanks for the contribution, and sorry for the slow response here.

The approach looks right — reusing SearchBox and gating it behind a searchable prop on ArrayFieldFilter keeps the change small and leaves the other filters untouched. A few things before this can go in:

1. Search query isn't reset when the dropdown closes

search lives in ArrayFieldFilter, which stays mounted — only the Menu children unmount. So after typing REQ-12 and closing the dropdown, reopening it still shows the filtered subset (and the same applies after the filter's Clear button). Worth resetting the query when the menu closes, and inside onClear.

2. changeDebounce={0}

This overrides the 300ms default, so every keystroke re-renders the whole option list synchronously. The list isn't virtualized, so on the thousands-of-tags reports this PR targets that's noticeable input lag. I'd just drop the prop and keep the default.

3. Empty state

When nothing matches, Menu.Section renders an empty <ul> — a blank dropdown that reads as broken. A short "nothing found" row would help.

4. Dead stopPropagation

The onClick/onMouseDown handlers on the search wrapper aren't needed: Menu only closes on clicks whose target is outside menuRef, and this div is inside the portal subtree (Menu/index.tsx, the handleClickOutside guard). They also swallow the click for every other document-level listener, so better removed.

5. Rebase

The branch conflicts with main — it's trivial, both sides appended a block at the end of ReportFilters/styles.scss. ArrayFieldFilter also picked up new consumers in the meantime (Severity, Resolution filters), worth a quick check that they still render as before.

A unit test covering the filtering (match, no-match, reset on close) would be good to have too.

@todti
Thanks for the review - addressed in the latest push:

1. Search resets when the dropdown closes and when Clear is used
2. Dropped changeDebounce={0} (keeps the default debounce)
3. Added a “No results” empty state for non-matching search
4. Removed the unnecessary stopPropagation handlers
5. Rebased onto latest main (styles conflict resolved). Severity/Resolution still use MultipleChoiceFieldFilter and are unchanged
6. Added unit tests for match, no-match empty state, and reset on close

Ready for another look when you have a moment.