COMMS: Update link objects to use new LinkInterface definition
BUILD: Add new dependency on QSignalSpy in TCPLink
APMToolBar: Update to use new getConnectionSpeed() API
QGC Log Player: Update to use new LinkInterface API
UAS: Updated the UASInterface API to align more with QGC.

This helps with supporting changes to common widgets and HIL simulation
PFD Widget: Updates to new UASInterface API
UAS: Update PxQuad to new UASInterface API
Map Widget: Update to use new AMSL & Relative Alt APIs
3DMap Widget: Update to use AMSL & Relative Alt APIs
Mission Widget: Update to use AMSL & Relative Alt APIs
Configuration: Set the GCS sys is to be 253 to identify logs from AP2
HIL Config: Update to use new HIL API in UASInterface.
Map Tool Widget: Fix to use new UASInterface API
Documentation: Fix #237, brought README.md up to date for building AP2 in windows
Log Replay: Fix for random crash involving not checking array size before accessing
Log Replay: Improved speed and position modifiers as well as cpu usage.

The Log replay thread now runs its own mavlink parser, which offloads
some of the CPU usage from the UI thread. This should make the UI a bit
more responsive when running the replay at higher speeds.

The position display has also been changed to be a user-settable slider,
for allowing the user to jump around in the log file. This will make
graphs look a bit odd if the user is constantly jumping, but that is to be
expected.
Status Bar: Removed hardcoded stylesheet for QGCStatusBar

TLog replay controls will now follow the current stylesheet colors properly.
Log Replay: Improvments to the UI, as well as the backend for mavlink handling

Changed the slider for speed to 5 buttons, 0.75X, 1X, 1.5X, 2X, and 5X for
log replay speed control.

Also fixed a bug where not all mavlink messages were being recognized by
the graph view, and none were being recognized by the Mavlink inspector
during log playback
Log replay: Added 10x speed button, and cleaned up unneeded code
Graph View: Fix for UI not refreshing, and added MODE string messages

@rolandbosa suggested an implementation to allow for MODE strings to be
displayed on the graph. While I couldn't directly pull in his change, I
have reimplemented the MODE display as he recommended.

There is also a small fix for the plot not updating properly twice a
second when it is on screen.