fix(robot-server, app): Fix ODD routing back to previous screen

[mjhuff]

Closes RQA-3036 and RQA-3038

Overview

The recent react-router update exposed an existing bug: MQTT did not properly publish a refetch to runs/:runId after a client sends a PATCH to runs/:runId. Although the exact reasoning concerning why the migration from history.push to navigate exposes this problem is unknown, this PR provides the necessary publish event to the app's top level redirection logic and prevents redirection back to the previous route. Note that this does mean we have to account for noticible client latency now, so this PR also adds loading state when "return to dashboard" is clicked.

Screen.Recording.2024-08-15.at.1.22.57.PM.mov

Test Plan and Hands on Testing

• Verified clicking "Run again" on the ODD routes the user to the correct location with no unexpected redirection elsewhere.
• Verified MQTT now sends a publish update after the app PATCHes run/:runId.

Changelog

• Fixed the ODD routing back to the previous screen after clicking buttons.

Risk assessment

low

[TamarZanzouri]

very nice! LGTM!