fix(robot-server): initialize fw update status_cache so we dont hang on bootup when client queries fw updates.

[vegano1]

Overview

The "instrument firmware update needed" modal was shown on bootup when a firmware update was required. This modal has a "Update Firmware" button that, when pressed, initiates the update for the attached instrument. However, since the updates have already been started internally, pressing the button does nothing until the first update is finished.

The main issue is that the /subsystem/updates/all request would hang until the first update was finished for ~2m, this happens because the start_update_process function called during bootup would hang waiting on provide_latest_progress which itself is waiting on to get a status report on self._status_queue.get() which blocks. Since the start_update_process acquires the _management_lock, once we call all_ongoing_processes from the client query we lock until an update is finished.

The problem is the "waiting to get the progress" of a specific update process from the hardware controller layer. The start_update_process function "queues" the firmware updates by creating the _UpdateProcess and then running the _update_task with TaskRunner.run in the background. This does not guarantee that the update will pass, but, as far as the robot server is concerned the update has been "queued".

So what this PR proposes is, when creating the _UpdateProcess in the _emplace method, that we initialize the status_cache: UpdateProgress with a default queued state. This way we don't block waiting on the response from the hardware controller, and the /subsystem/updates/all request can return.

Closes: RQA-2574

Test Plan

• Make sure that firmware updates are automatically initiated when the robot boots up
• Make sure that firmware updates are started from the ODD during the attachment flow
• Make sure that firmware updates required modal is displayed when an instrument is attached outside the attach flow
• Make sure that firmware update required modal is NOT shown when the robot boots up and an instrument needs an update, instead we should see the "Updating x Module Firmware..." modal.

Changelog

• add status_cache arg to _UpdateProcess class so we can have an UpdateProgress state when creating the update

Review requests

• Does this approach make sense?
• Any implications I might be missing?

Risk assessment

Low, but will need additional testing as this touches firmware updates

[smb2268]

This approach makes sense to me! Thanks for all of the investigation into this one 🙏🏻

[caila-marashaj]

lgtm- this seems like it'll be really nice to have

[sfoster1]

Looks good to me, nice!