Misc ideas for improvements to updating

[hello-binit]

Here's a list of unrelated ideas for improving the updating software UX:

• Updaters should check if they themselves are up-to-date before doing anything else
  • e.g. Pip will tell you to run pip3 install -U pip to upgrade itself if an update if available
  • Critical software updaters should should refuse to update if it sees that it itself is not up-to-date. E.g. the firmware updater can leave the robot in a soft-bricked state if it is an older version, unaware of some change in the system and/or hardware.
• On the docs, before the firmware update, always update factory tools first
• Often system check says 'notbe'. 'notbe' should have a space between it.
• System check skews towards saying your software is up-to-date, even if it isn't. This is due to caching during homing. Should not trust a cache > 5 days old.
  • should be explicit ("as of 5 days ago, your software is up-to-date. To get a more recent estimate, run a homing")
• The docs are incorrect: https://docs.hello-robot.com/0.3/software/updating_software/#identifying-your-current-software, points to the older tool
• we could branch flow in the updating doc, based on the version you have
  • we could have a breaking CLI renaming intentionally, to clearly separate "new flow" vs. "old flow"
  • old flow is documented well, in collasible sections
• we need to make explicit recommendations about Apt and Realsense firmwares
  • we should recommend keeping Apt repositories up-to-date