This wasn’t quite coded correctly. Mavlink needs heartbeat first, then
the shell command will be issued.

Instead us a Toolbox concept which hangs off of QGCApplication

- Must end in Log for *Log.debug=false to work in filter rules

- Fixed bugs found to unit test

- select active vehicle
- arm/disarm
- select flight mode

- fix bugs found by test
- Implemented Mock mission item protocol in

Link ids were being used interchangeably with the mavlink channel for
the link. Link ids handed out as a numerically increasing integer. Once
the counter went past MAVLINK_COMM_NUM_BUFFERS all hell would break
loose and cause memory corruption.

If it doesn’t exist it will be prefilled with all registered categories
set to false

The goal of this first installment is to organize the code a bit so it's more readable,
clean up a bit of left over cruft, and manage link configurations (and links in general).

This prevents mavlink signals from being emitted after link is
disconnected

Plus a large number of other changes to allow for orderly shutdown of
objects without crashes or asserts. This is need for unit tests to
create/delete global state around every test.