app(fix): Fix error recovery on desktop DQA

[mjhuff]

Overview

As with the previous DQA tickets, the proof is linked in each ticket. There are two important fixes, the first two commits.

Commit 1 - RQA-3632 Step number doesn't translate 1-1 to 0 based indexing :)
Commit 2 - RQA-3642 The "meaty" one. QA hasn't seen alpha.3, so they haven't reported it yet, but there are times we accidentally show a generic "error" recovery modal after cancelling the run, and that's because we now gate recovery behind there being a failed command OR there being a stop requested run status. The problem is these data are derived from separate HTTP resources, so there can be torn state, in which we get the flicker behavior shown in the ticket video. The solution is just to reduce the complexity of the hook. We don't need intermediate state, hasSeenAwaitingRecovery, as this creates an extra render cycle that leads to the flickering.
Commit 3 - RQA-3629
Commit 4 - RQA-3627

Test Plan and Hands on Testing

• See tickets. For commit 2, I did test a lot of permutations of ER.

Risk assessment

low

[sfoster1]

useLayoutEffect looks sick