Fix issue with `idle` (Gemini code review comment)

In TanStack Query v5, the idle status has been removed. Disabled queries now start with a pending status. This change causes your fromReactQuery function to incorrectly return a "busy" state for disabled queries, which will likely result in a misleading UI (e.g., showing a spinner for a query that isn't running).

To fix this, you can differentiate between a truly pending (loading) query and a disabled one by using the isLoading flag, which is true only when a query is pending and fetching.

I recommend updating the function to accept isLoading and handle the disabled case separately, like this:

export function fromReactQuery(status: QueryStatus, isLoading: boolean): SearchState {
  // A disabled query in v5 has status 'pending' but isLoading is false.
  // This check restores the behavior of the old 'idle' status.
  if (status === "pending" && !isLoading) {
    return undefined;
  }

  switch (status) {
    case "error":
      return "error";
    case "pending":
      return "busy";
    case "success":
      return "ok";
  }
}

You will also need to update the call sites to pass this value. For example, in TracksForm.tsx:

const { status, isLoading, ... } = useGeoJSON(...);
const state = fromReactQuery(status, isLoading);

Find the fromReactQuery function and its call sites, including TracksForm.tsx where useGeoJSON provides the query state. Read how status and isLoading are currently obtained, then update the disabled-query handling so pending but non-loading queries are not reported as busy. Verify the affected UI no longer shows a loading state for disabled queries.