[ATLAS-397] Enhancement: input debounce for library and browse

[codeon89]

What this changes

Apply search input debouncing for Library and Browse mode. Typing should stays smooth and responsive instad of lag due to refresh, or re-rendering, while filtering/fetching waits for the user to pause. Clicking clear immediately resets the list without waiting. Remove the existing fetch debounce in browse mode that will cause duplicate delay when this new change come in.

Why

#397

Updating activeFilters.text on every single keystroke was triggering a full filter pass in the Library (and queueing catalog API requests in Browse) for every character typed. On larger libraries, this caused input lag and visible UI stuttering as the catalog re-fetched and cleared grid views. Moving the debounce logic before setActiveFilters via a shared hook fixes the delay without dropping input state.

How it was tested

• Added tests that cover this change
• For a fix: the regression test fails against the unfixed code
• npm run check passes locally
• New functions and IPC handlers have comments explaining why
• CHANGELOG.md updated
• This PR targets nightly, not main

AI assistance

• No AI was used on this change
• AI was used on this change

Tool and model: VSCode auto free

What it wrote: src/hooks/useDebouncedSearch.js hook (handles input state and reset signal), search component wiring in SearchBox.jsx and SearchSidebar.jsx, App.jsx signal routing, CHANGELOG.md entries, and the regression tests in tests/search-debounce.test.jsx.

What you verified yourself:
Manually tested search behavior on the client to confirm input responsiveness, verified that clearing resets instantly, and confirmed all regression tests pass.

[codeon89]

Closing this for now as the existing behavior is not behaving too bad with the current database. The new change will add some complexity while it is not required for the current performance. Previous test issue was based in dev mode with console on.

[codeon89]

Originally close this as when i test original it stopped happening but I noticed the issue surface again after browsing for a while, so re-opening this.

[codeon89]

Still couldn't reproduce it, only got by chance, but it feels like I didn't trigger any yet when in packaged app, but does when in dev mode (console close) somehow. Closing this again for now.

[codeon89]

This really keeps happening to me, especially when you keep having wishlist / other tag filter. Plus from the logic stand point it makes sense (the downside is extra complexity but if it's what needed I think it's worth) so I am reopening this again 🙆