chore: Continue ignoring navigate() Promise

> Because React 19 will have first-class support for handling promises
> in the render pass (via React.use and useAction), we are now comfortable
> exposing the promises for the APIs that previously returned undefined

https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#exposed-router-promises

... which means we can void the return value without change in behavior.

frontend/src/pages/Job.tsx

@@ -76,7 +76,7 @@ const JobStatus: FunctionComponent<{
     if (props.job.settings.debugLogging != null) {
       params.set('debugLogging', props.job.settings.debugLogging.toString())
     }
-    navigate(`/trigger?${params.toString()}`)
+    void navigate(`/trigger?${params.toString()}`)
   }, [props.job, navigate])
 
   const common = (

frontend/src/pages/Trigger.tsx

@@ -43,7 +43,7 @@ export const Trigger: FunctionComponent = () => {
   // redirect to job page when jobData is available
   useEffect(() => {
     if (jobData != null) {
-      navigate(`/jobs/${encodeURIComponent(jobData.namespace)}/${encodeURIComponent(jobData.name)}`)
+      void navigate(`/jobs/${encodeURIComponent(jobData.namespace)}/${encodeURIComponent(jobData.name)}`)
     }
   }, [jobData, navigate])