Previously link were just destroyed

Renamed some variables.
Removed unused joystick settings stuff.
Deleted unused actions.

This function is called automatically when a QSettings object is destroyed,
so is rarely needed to be called explicitly.

There are still some cases where
a QSettings object is passed-by-reference, so there I left the sync() calls as
it's unclear how permanent those objects are and if they'd call sync() before
application shutdown

Fixes bugs with savings settings for the window state, theme, UAS-connected view, and low-power mode.
Also removes some unneccesary logic that attempted to handled unclean shutdowns, which I haven't
been able to reproduce.

It was a poor proxy for better coding around the problem of bad settings or the lack of
settings on first-run.

No functionality changes in this code, just code clarify improvements.

Splash screen is optional. Also remove some unused class definition.

- allow unit tests to use QGCApplication
- clear global singletons for each unit test run

Subclass of QMessageBox which re-implements the static public
functions. There are two reasons for this:
1) The QMessageBox implementation on OSX does now show the title
string. This leads to message boxes which don't make much sense. So on
OSX we set title to text and text to informative text.
2) If parent is NULL, we set parent to MainWindow::instance. This
prevents message boxes which can go behind MainWindow

Do not dynamic cast or de-reference QObject, since object is either in
destructor or may have already been destroyed.

Plus change to use QGCFileDialog

- Logging now always on to temp file
- User prompted to save temp file after disconnect
- Orphaned temp logs checked for on boot
- Logs saved to new save file location
- Log file starts/stops with first and last connnection

Also fixed bug in loadStyle

The dark css is the master and contains all style information. The
light css is the slave and only contains color information.

This is the Pixhawk research board, not the PX4 production board.

Settings versioning is handled at the uppermost level with a version
stamp.

No major functionality changes.

Tried to order items in order of importance.
Also all perspectives now have their own shortcuts.

Both on the backend (replaced with DEFAULT view) and on the front end (removing UI menu items).