Instead of resetting all parameters when some parameter change, explicitly define list of parameters that must be requested when a given parameter change.

Retry requests for storage and capture info.

Removed guess work from what parameters must be refreshed/updated when some other parameter changes. Added a "reset" flag that indicates when a certain parameter changes, the list must be reloaded.
Don't send a signal when setting a fact if the new value is the same.

Fixed inverse logic in camera parameter retry count
Skip close timeout if not Windows

Increase param ack timeout.
Retry when param set failed.

This needs Qt 5.9. Do not merge it yet.

* If new Survey is set to altitude fixed value then use mission default
altitude
* If the user applies a new altitude to the entire mission change
surveys to fixed altitude and apply altitude

This way if the user switches away from manual the altitude is preserved

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.