GCS Log Replay: Fix replay of android log files

The android log files use the android system time which means it
can start at very large numbers, whereas GCS logs start at zero.
To fix this the time of the first timestamp is subtracted out.

Also the times were signed which is inappropriate, so they are
all converted to quint32.

As a side note the way this code is written, it is _extremely_
brittle to ill-formatted logfiles because it doesn't use the
UAVTalk parser or try and maintain sync.  I also removed a
redundant set of checks on the order of timestamps as this is
done during loading and also didn't respond well to the large
timestamps from android.
Merge pull request #436 from peabody124/gcs_android_replay_fix

GCS Log Replay: Fix replay of android log files
GCS: Fix typo for optional SDL
Revert "GCS: Fix typo for optional SDL"

This reverts commit ddbbc02aae86738edb26710687ac7dbbbf94aca4.
Revert "Merge pull request #440 from kubark42/gcs-control-via-gcsreceiver"

This reverts commit c2fba6ea63fdb17a99be6750297e384ff5f80f2e, reversing
changes made to a24176f9e7c43cf777d3b5fc65d9ca30d1b71907.

The way SDL was reenabled was broken.  Reverting this merge.
RevoCalibration: Get rid of this UAVO and roll into SensorSettings

InertialSensorSettings was renamed to SensorSettings since Mag is not
inertial which is what caused most of the LOC changes.
GCS Calibration: Use SensorSettings instead of InertialSensorSettings