fix(webapp): keep controlled TimeFilter from falling back to the URL

When TimeFilter is used in controlled mode (onValueChange provided), it now
takes period/from/to only from props instead of falling back to the URL
search params. Selecting a custom date range in the model detail panel (which
sets period to undefined) no longer reverts the filter display to the
page-level URL period.

Author: ericallam

apps/webapp/app/components/runs/v3/SharedFilters.tsx

@@ -375,9 +375,13 @@ export function TimeFilter({
   valueClassName,
 }: TimeFilterProps = {}) {
   const { value } = useSearchParams();
-  const periodValue = period ?? value("period");
-  const fromValue = from ?? value("from");
-  const toValue = to ?? value("to");
+  // In controlled mode (onValueChange provided) the caller owns all three values via local
+  // state, so don't fall back to the URL — otherwise selecting a custom date range (which
+  // sets period to undefined) would read the page-level URL period and override the range.
+  const controlled = onValueChange !== undefined;
+  const periodValue = controlled ? period : period ?? value("period");
+  const fromValue = controlled ? from : from ?? value("from");
+  const toValue = controlled ? to : to ?? value("to");
   const triggerRef = useRef<HTMLButtonElement>(null);
 
   useShortcutKeys({