sdlog2_dump.py didn't know what to do with data types "d" and was causing errors when trying to dump APM .bin files to .csv.

The latest version must have gotten lost in the merge.

If mavlink_log calls follow close after each other a later one will
replace the previous one. Therefore do a quick usleep to get the
calibration status out the door.

The logging into a text file was commented out in the recent changes but
is added back in with this commit.

The mavlink log didn't seem to be used anyway. This should fix jenkins.

The mavlink_log API changes lead to changes in all drivers/modules using
it.

The header file was not in source with the source file.

This moves the mavlink_log interface from ioctl to uORB and enables the
mavlink statusmessage output for Snapdragon. The API changes will lead
to changes in all modules that are using it.

This brings better support for device ids.

This fixes some regressions on the calibration using NuttX, especially
considering the PRIME param and the device ids.

The PRIME param got lost on the way of the refactoring.

The PRIME param got lost on the way of the refactoring.

Instead of using a uORB topic with the calibration values published in
sensors and consumed by the DriverFramework driver wrappers, let's just
use the the params directly. This is quite a rough change and needs
definitely some cleanup and refactoring.

E.g. instead of defining a gyro_scale struct in drv_gyro.h, use the
gyro_calibration message.

Trailing whitespace all over.

This adds uORB messages to publish calibration data by sensors which is
then consumed by the sensors. Currently this is only used on Snapdragon
and guarded by QURT ifdefs.