fix(web): serialize location.search to prevent [object Object] in history

TanStack Router's useLocation() returns location.search as a parsed
object, not a string. Concatenating it with strings caused JavaScript
to call toString(), producing "[object Object]" in URLs and history.

Use serializeSearch() utility (already used in NavigationTracker and
use-user-interactions) to properly convert the search object to a
query string format.

Author: Mearman

apps/web/src/hooks/useNavigationEnhancements.ts

@@ -6,6 +6,8 @@
 import { useLocation, useRouter } from "@tanstack/react-router";
 import { useCallback, useEffect, useRef, useState } from "react";
 
+import { serializeSearch } from "@/utils/url-decoding";
+
 interface NavigationState {
   canGoBack: boolean;
   canGoForward: boolean;
@@ -20,7 +22,7 @@ export const useNavigationEnhancements = () => {
   const [searchHistory, setSearchHistory] = useState<string[]>([]);
 
   // Track navigation history
-  const currentPath = location.pathname + location.search + location.hash;
+  const currentPath = location.pathname + serializeSearch(location.search) + location.hash;
 
   useEffect(() => {
     const lastPath = historyRef.current[historyRef.current.length - 1];