chore(ui): unify filter search and batch patterns

[alejandrobailo]

Context

Resource filters need to converge on the same interaction model already used in findings. Before touching the Resources view, the shared filter primitives needed to support local option search and predictable dropdown behavior across the app.

Screen.Recording.2026-04-23.at.14.20.57.mov

Description

This PR updates the shared filter building blocks used by table and provider filters.

• enable local option search in shared multiselect dropdowns
• keep the trigger value stable while the dropdown search input is active
• auto-scroll to the first visible match when filtering long option lists
• wire the shared behavior into table filters and provider filters
• keep the change UI-only: no backend contract, URL shape, or query param semantics change

Steps to review

1. Open any findings view with multi-select filters and search inside a long dropdown.
2. Confirm the selected value shown in the trigger does not change while typing in the dropdown search input.
3. Confirm the list scrolls to the first visible match when the typed query narrows the options.
4. Open Cloud Providers and verify the same searchable dropdown behavior is available there.
5. Run:
   • cd ui && pnpm test:run components/shadcn/select/multiselect.test.tsx components/ui/table/data-table-filter-custom-batch.test.tsx components/providers/providers-filters.test.tsx
   • cd ui && pnpm typecheck

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

SDK/CLI

• Are there new checks included in this PR? No
  • If so, do we need to update permissions for the provider? Please review this carefully.

UI

• All issue/task requirements work as expected on the UI
• Screenshots/Video of the functionality flow (if applicable) - Mobile (X < 640px)
• Screenshots/Video of the functionality flow (if applicable) - Table (640px > X < 1024px)
• Screenshots/Video of the functionality flow (if applicable) - Desktop (X > 1024px)
• Ensure new entries are added to CHANGELOG.md, if applicable.

API

• All issue/task requirements work as expected on the API
• Endpoint response output (if applicable)
• EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable)
• Performance test results (if applicable)
• Any other relevant evidence of the implementation (if applicable)
• Verify if API specs need to be regenerated.
• Check if version updates are required (e.g., specs, Poetry, etc.).
• Ensure new entries are added to CHANGELOG.md, if applicable.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

🔒 Container Security Scan

Image: prowler-ui:07f8e4f
Last scan: 2026-04-23 12:25:20 UTC

✅ No Vulnerabilities Detected

The container image passed all security checks. No known CVEs were found.

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy