Remove/comment off debug output pollution

Some crazy shit in UAS.cc was using an array of 256 bytes to handle received messages and mapping them to components. Well, any message ID over 255 would cause a buffer overrun.

Remove debug output
Fact enumStrings and enumValues can not be changed independently. Therefore you only need one signal.

Pulling mavlink with a reversal for the CAMERA_IMAGE_CAPTURED message. It's now back as it was so it won't break existing code.
The pull also brought changes to the GPS_RAW_INT message. Only MockLink uses. I entered zeros for all new fields.

Handle initial storage
Handle image/video capture and storage.

Hide "Save Path" as it breaks the UI in General Settings.

Helps battery life

PX4 Firmware plugin: First try to switch flight mode, then arm if successful - which is a lot safer than arming and then seeing if we can switch modes.

Firmwareplugin: Trim retry period to something that matches closer the users attention and is still long enough to allow for multiple heartbeats to pass through