Test: increase test coverage of robot update UI

[mcous]

overview

A large chunk of our manual testing burden is dedicated to testing a large test matrix trying to make sure the UI behaves (e.g. when are release notes displayed?) in various different cases of app / robot version mismatches.

This UI testing is less important than ensuring the updates are successfully applied, so it's a good candidate for shifting the burden over to unit tests so the manual testing can focus on actual critical functionality.

acceptance criteria

As much as arbitrary coverage thresholds aren't necessarily a recipe for success, we clearly need something here. Let's call it:

• Coverage of robot-update related app and app-shell code is >= 80%

implementation details

These files / directories contain most, if not all of the app-side robot update functionality.

• app-shell/src/buildroot
  • Current line coverage: 0%
• app/src/buildroot
  • Current line coverage: 83%
• app/src/components/RobotSettings/InformationCard.js
  • Current line coverage: 0%
• app/src/components/RobotSettings/UpdateBuildroot
  • Current directory line coverage: 0%

Those coverage numbers are pretty awful! Let's get this fixed up

[mcous]

TODO: break this ticket up into smaller chunks. Parts of this have been addressed in various feature buildouts (e.g. disable app update notifications)

[mcous]

Once 4.0 is released, re-evaluate the coverage numbers and/or the need for this ticket (in favor of smaller, more specific tickets)

[mcous]

Done enough to need new tickets now that app e2e testing is moving forward