Improve error checking and reporting

[MattCummings0517]

In general, the ceti-tag-data-capture application needs to be improved for more robust error checking and appropriate handling

[MattCummings0517]

Tag 1 developed a problem with i2c bus 1 in the field during the July 2022 expedition at some point - all devices are not appearing, so it is as if the bus is hung. The initialization checks failed to detect the problem, so this is clearly an area where an improved self check would be beneficial, and then some sort of attempt at resetting the bus. Right now, it is not clear if there is a hard failure or just a stuck i2c bus.

[MattCummings0517]

As a follow up, there is some evidence that water got in around the depth sensor on v2.1 Tag #1 and may have damaged it. Both the RTC and the depth sensor are non-responsive, but other devices on the i2c are. This suggests a possible disconnect - it is interesting to note that the RTC and depth sensor are located in the same general physical location on the board. The tag continued to work otherwise - audio is OK and other sensors are reporting reasonable values.

As far as this issue, a health check report or similar might be nice to have...