Move writing of compass log messages into compass library

[peterbarker]

Summary

Mirror structure used by baro already for logging

Classification & Testing (check all that apply and add your own)

• Checked by a human programmer
• Non-functional change
• No-binary change
• Infrastructure change (e.g. unit tests, helper scripts)
• Automated test(s) verify changes (e.g. unit test, autotest)
• Tested manually, description below (e.g. SITL)
• Tested on hardware
• Logs attached
• Logs available on request

Still get log messages in SITL:

1970-01-01 10:00:09.03: MAG {TimeUS : 9039716, I : 0, MagX : 224, MagY : 80, MagZ : -528, OfsX : 5, OfsY : 13, OfsZ : -18, MOX : 0, MOY : 0, MOZ : 0, Health : 1, S : 9039716}
1970-01-01 10:00:09.03: MAG {TimeUS : 9039716, I : 1, MagX : 224, MagY : 80, MagZ : -528, OfsX : 5, OfsY : 13, OfsZ : -18, MOX : 0, MOY : 0, MOZ : 0, Health : 1, S : 9039716}
1970-01-01 10:00:09.03: MAG {TimeUS : 9039716, I : 2, MagX : 224, MagY : 80, MagZ : -528, OfsX : 5, OfsY : 13, OfsZ : -18, MOX : 0, MOY : 0, MOZ : 0, Health : 1, S : 9039716}

Board,plane
MatekF405,-16

Description

Moves the implementation from A to B - same pattern we use for the baro library.

Doing this to simplify a PR moving logging around.

[IamPete1]

I know this is a existing problem, but I really want logs if my compass is not healthy.

[peterbarker]

I will review and almost certainly approve a PR which logs compasses even if they are all unhealthy.

[peterbarker]

909e5d6 - we used to not log any unless the first was healthy!