fix(launcher): guard setSettingsLoaded in catch on unmount

The catch branch of the initial settings-load effect was calling
setSettingsLoaded(true) without checking the disposed flag, which would
trigger React's setState-on-unmounted-component warning if the IPC
rejected after the hook unmounted (hot-reload, fast navigation).
Mirrors the existing guard in the .then branch.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: shobhit99

src/renderer/src/hooks/useBrowserSearch.ts

@@ -183,7 +183,7 @@ export function useBrowserSearch(_currentQuery: string): UseBrowserSearchResult
         setSettingsLoaded(true);
       })
       .catch(() => {
-        setSettingsLoaded(true);
+        if (!disposed) setSettingsLoaded(true);
       });
     return () => {
       disposed = true;