Fix host table staleness on id change and redundant fetches for finished invocations

When React Router reuses JobInvocationDetailPage for a different job via
breadcrumb navigation, the host table guard effect was not checking for id
changes, leaving the table stale. Add a prevId ref so an id change triggers
a re-fetch alongside the existing filter/status guards.

TemplateInvocation was unconditionally calling dispatchFetch() on every
expand, even for invocations that were already finished and had a full
response in the Redux store. Guard dispatchFetch() behind
response?.finished !== true to skip the extra HTTP request on
collapse→expand cycles for completed invocations.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: adamruzicka

webpack/JobInvocationDetail/JobInvocationHostTable.js

@@ -69,6 +69,7 @@ const JobInvocationHostTable = ({
   const [expandedHost, setExpandedHost] = useState(new Set());
   const prevJobFinished = useRef(jobFinished);
   const prevFilter = useRef(initialFilter);
+  const prevId = useRef(id);
   const pollTimeoutId = useRef(null);
   const currentPollParams = useRef({});
   const jobFinishedRef = useRef(jobFinished);
@@ -257,10 +258,12 @@ const JobInvocationHostTable = ({
   useEffect(() => {
     const filterChanged = initialFilter !== prevFilter.current;
     const statusChanged = jobFinished !== prevJobFinished.current;
+    const idChanged = id !== prevId.current;
 
-    if ((filterChanged || statusChanged) && initialFilter !== '') {
+    if ((filterChanged || statusChanged || idChanged) && initialFilter !== '') {
       prevFilter.current = initialFilter;
       prevJobFinished.current = jobFinished;
+      prevId.current = id;
       filterApiCall();
     }
   }, [initialFilter, jobFinished, id, filterApiCall]);

webpack/JobInvocationDetail/TemplateInvocation.js

@@ -106,14 +106,16 @@ export const TemplateInvocation = ({
     }
 
     if (isExpanded) {
-      dispatchFetch();
+      if (response?.finished !== true) {
+        dispatchFetch();
+      }
     }
 
     return () => {
       cancelled = true;
       clearTimeout(timeoutRef.current);
     };
-  }, [isExpanded, dispatch, templateURL, hostID]);
+  }, [isExpanded, dispatch, templateURL, hostID, response]);
 
   if (!response || (status === STATUS.PENDING && isEmpty(response))) {
     return <Skeleton data-testid="template-invocation-skeleton" />;