Unit Tests run from there own QSettings space

This is done by tweaking the application name when running unit test

Bumped developer version

Update for 32 bit Google earth information

I initially change version numbers incorrectly. Should have left stable
at 2.1 and only bumped Developer to 2.2. This leaves Stable at 2.2 and
Developer at 2.3.

Hiding splash screen now handled by QGCFileDialog/QGCMessageBox

Conflicts:
	src/QGCFileDialog.cc

Also restructured code to remove duplication

Fix param crash and connect/disconnect

Also restructured code to remove duplication

Fix broken native file dialogs

Test all views on the toolbar

Work around qRegisterMetaType race condition

There appears to be a threading issue in qRegisterMetaType which can
cause it to throw a qWarning about duplicate type converters. This is
caused by a race condition in the Qt code. Still working with them on
tracking down the bug. For now we register the type which is giving us
problems here while we only have the main thread. That should prevent
it from hitting the race condition later on in the code.

QSqlDatabase::addDatabase not thread safe with plugin

Although the method is marked as thread safe in the docs, if you use a
database plugin it ends up not being thread safe.

Refactoring on MainWindow's view and settings code

- Use pkgconfig on linux to avoid break build on undefineds

Accel calibration wizard fix

Hopefully fix thread safety issue in opmapcontrol

Operator = is not thread-safe, but copy constructor looks to be. This
is causing an intermittent crash.

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

Simple starting point to view testing

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.