bug(ui): Search modal triggers immediately on keydown without debouncing / interrupts typing

Bug Description

When typing into the search modal on the Wasmer website (wasmer.io), the search executes instantly on every keypress without proper debouncing. This disrupts text entry and prevents completing multi-character search terms naturally.

---

Steps to Reproduce

1. Open the search modal on wasmer.io.
2. Type a search term quickly (e.g., "python" or "luca").
3. Observe the input handling behavior during rapid keypresses.

---

Expected Behavior

The search input should allow continuous typing and apply a debounce delay (e.g., 200ms–300ms) after the user stops typing before triggering network requests or heavy DOM re-renders.

---

Actual Behavior

The input triggers state updates or network requests immediately on every keystroke, disrupting typing focus and locking up character input before a full word can be typed.

---

Suggested Solution

Wrap the search query state or API dispatch in a debounced handler (or a standard useDebounce hook) to ensure search queries trigger only after a brief pause in typing.