fix(app): Enable robot update even if API reports up-to-date

[mcous]

overview

This PR is also serving as the ticket. With the addition of firmware updates in the robot update flow, we ran into an issue where sometimes, the firmware would not update (for various valid / invalid reasons). However, because the API update usually succeeds, /health would report that the robot was up to date, and the update button would become disabled. This would then remove any firmware upgrade path from the user until the next API update.

Until we figure out a more refined approach to separating and communicating smoothie firmware, this PR removes the button disable logic and allows the user to send the update request even if the robot appears up to date.

changelog

• fix(app): Enable robot update even if API reports up-to-date

review requests

Tested on Sunset. Robot update should work even if robot is already up to date

[Kadee80]

🎎

[codecov]

Codecov Report

Merging #1721 into edge will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             edge   #1721      +/-   ##
=========================================
- Coverage   35.01%     35%   -0.02%     
=========================================
  Files         344     344              
  Lines        5646    5648       +2     
=========================================
  Hits         1977    1977              
- Misses       3669    3671       +2

Impacted Files	Coverage Δ
...pp/src/components/RobotSettings/InformationCard.js	0% <ø> (ø)	⬆️
app/src/components/RobotSettings/UpdateModal.js	0% <0%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ccf4881...171dcde. Read the comment docs.