Most math and backend storage was floats anyways, so most of these changes just half the data copied during function calls without reducing precision.

Replaced with only 1 output message with the result of the first serial port scan.

In the logplayer, the data stream is read ahead for messages, which is used to determine the size of the output bytearrays. Previously, this wasn't done correctly resulting in non-ideal behavior. Now, the next message is scanned properly, so the only bytearrays that are emitted from QGCMAVLinkLogPlayer are MAVLink messages in their entirety. This also has the benefit of skipping invalid/corrupted messages in the log that's being played back.

Because the indexes into the stackedwidget are all wrong

There were two separate actions for the simulation view, leading to
strange behaviour when it was selected.