fix(cmd-k): Remove redundant sync effect that broke no-results detection

The separate prevFilteredCount sync effect ran before the no-results
effect in declaration order, zeroing out the previous value before
the check could compare it. The no-results effect already updates
prevFilteredCount itself, so the sync effect was both redundant and
harmful.

Author: jshchnz

static/app/components/commandPalette/useCommandPaletteAnalytics.tsx

@@ -61,12 +61,6 @@ export function useCommandPaletteAnalytics(filteredActionCount: number): {
     analyticsState.current.state = state;
   }, [state]);
 
-  // Sync filtered count to ref so the debounce timer reads the latest value
-  // without restarting on async result changes (e.g. DSN lookup)
-  useEffect(() => {
-    analyticsState.current.prevFilteredCount = filteredActionCount;
-  }, [filteredActionCount]);
-
   // Debounced query tracking
   useEffect(() => {
     const s = analyticsState.current;