This reverts commit e003dd7a.

Anton and I noticed that the message view stops autoscrolling properly
sometimes when there's a high frequency of arriving messages. This
should fix that problem.

Also fix a few compiler switch warnings

Fixed Compiler Error C2864 - only static const integral data members can be initialized within a class

Add map type selector menu; use Bing maps by default; zoom to a more
human scale on Go Home

Fixed styling of the toolbar, specifically coloring and sizing of the buttons, and made the labels aware of the current window theme. Also made some changes to updating the toolbar when switching UASes or when UASes disconnect/reconnect.

Improved UI when no joysticks are connected. Also removed hotplugging support for joysticks as it wasn't working, though SDL2 should fix that.

Vastly improved the joystick documentation, removed some redundant/unnecessary code, and fixed a couple of small bugs. This code should be ready for live testing.

All UI elements in the JoystickWidget window are now updated properly when switching UASes, which was the last major issue with this code. A single small bug remains involving the UI not updating the axis values when switching joysticks until the axis is moved.

Have settings loaded/stored correctly for all joysticks based on their UAS type and autopilot type. Switching between UASes doesn't work right yet, however.

The default UAS.cc now lists available actions that it can be commanded. These are polled by the Joystick Configuration window for each joystick button so that they can be assigned to trigger this action. Button presses don't yet trigger these actions, nor are they stored and reloaded on UAS switch.

The settings for each joystick are loaded and saved on switch. The state of the enable joysticks checkbox is not saved yet, however, though it should really be tracked by JoystickInput so that it can sleep more when joysticks are disabled.

Restored range limiting to the throttle channel. Now if the UAS can't reverse, the throttle can be set to only use the positive range of the axis (useful with auto-centering control sticks) or to use the full range (for sticks that hold position).

The joystick code now understands if a UAS can reverse or not (based on UASInterface::systemCanReverse) and scales the joystick input accordingly. This isn't ideal on auto-centering axes and so the limit-range code should be brought back as an option for the throttle channel.

The UASInterface now defines a systemCanReverse() function for indicating if the UAS is capable of commanding a reverse thrust.