fix(ui-react): use server-side filtering for device search

[luizhf42]

What

Device search on the tenant device list page now queries the API with a base64-encoded filter instead of filtering client-side.

Why

The previous implementation filtered devices locally after fetching, which only searched within the current page (10 devices). With more than one page of devices, search results were incomplete. The Vue UI already sends server-side filters correctly; this aligns the React UI with that behavior.

Changes

• useDevices hook: Merged buildTagFilter into a unified buildFilter(search, tags) that combines name and tag filters into a single base64-encoded array. Added search param to the hook interface.
• Devices page: Replaced local .filter() with a debounced (300ms, trimmed) search input that passes the query to useDevices for server-side filtering. Page resets to 1 on new input.
• Tests: Added unit tests for buildFilter covering search-only, tags-only, combined, and empty-input cases.

Testing

• Search for a device name that exists beyond the first page of results — it should now appear
• Verify whitespace-only input does not trigger an API call
• Confirm tag filtering still works independently and in combination with search

[github-actions]

Claude finished @luizhf42's task in 3m 27s —— View job

---

Code Review Complete

Reviewed 3 files across code quality, security, testing, TypeScript/React patterns, and architecture — no issues found. The code looks good as-is.

Highlights:

• buildFilter cleanly unifies name + tag filters into a single base64-encoded array matching the backend's expected format (pkg/api/query/filter.go)
• Debounce implementation is correct with proper cleanup
• Tests cover all meaningful input partitions
• No breaking changes to existing callers of useDevices (all new params are optional with defaults)
• Filter format is consistent with the Vue UI's existing approach

---

If you push additional changes and want a new review, tag @shellhub-io/admin and a team member can trigger it.