New service: Create a service for general health monitoring

[Williangalvani]

Proposa:

Create a new service. This would be responsible for checking the general vehicle's health. Such as:

• Warn user on:

  • Low disk space
  • High Memory usage
  • Unexpected packet loss
  • Extensions hogging too many resources
  • Corrupt configuration files
  • Vehicle reset to factory (Notify user via mavlink when blueos is in factory mode  #2236)
  • Kernel errors on dmesg (Warn user about USB devices intermittently reconnecting  #3583) (We should check for issues on kernel logs and warn the users when they open BlueOS again #3304) (Wifi: we should warn users when trying to open a hotspot on a NO-IR channel #3017)
  • low/over voltage
  • Missing vehicle calibrations (vehicle setup should warn users if internal Compasses were mistakenly set up as external. #1672)
  • updates available (Warn user to update bootstrap if running latest stable version.  #2481)
  • usb devices connection/disconnection
  • Allow extensiosn to publish data, too (DVL too hot comes to mind).

• Optional: allow picking "output channel" for each warning. I'd like low/over voltage and dvl warnings to be pushed to telegram, because I'm distracted sometimes

I imagine we could do this in Robyn so we don't further harm our boot times

[patrickelectric]

Allow extensions to publish data

We could do it via zenoh

[Williangalvani]

(I think) we agreed on having this be an data aggregator, which will fetch/receive data from the other services and publish it via mavlink/zenoh/telegram/email/smoke signals

[ES-Alexander]

... publish it via mavlink/zenoh/telegram/email/smoke signals

I think Zenoh (and maybe MAVLink) would be fine as what the service itself implements. External connectivity seems better managed by some non-core component (e.g. an Extension or Plugin) that gets its info from one of those outputs.