_finalize methods need information which is not available if all you
have is a mavlink_message_t

- Now responds to request_list using a worker routine to send out
params one at a time
- Support for failure modes for unit testing

- Delay gps position for better testing
- Longer delay on home position

This mechanism automatically queues data into the correct thread where necessary, otherwise the method is invoked directly with low overhead.

At the same time remove the UDP socket event workaround. It is not a problem.

Plus other auto connect bug fixes

There are many ways of iterating over lists in C++/Qt.
In the specific case of QStrings, it is known [1] that using
foreach with const references avoids the creation of new
QString objects in each iteration, reducing the time consumed
by the loops.

[1] https://blog.qt.io/blog/2009/01/23/iterating-efficiently/Signed-off-by: Anselmo L. S. Melo <anselmo.melo@intel.com>

- Pervasive change to automatically connect to known board types
- Lots of additional changes along with this:
- More exposure of objects/properties to Qml
- Much restructuring in LinkManager and LinkManager clients

- Pervasive change to automatically connect to known board types
- Lots of additional changes along with this:
- More exposure of objects/properties to Qml
- Much restructuring in LinkManager and LinkManager clients

- Pervasive change to automatically connect to known board types
- Lots of additional changes along with this:
- More exposure of objects/properties to Qml
- Much restructuring in LinkManager and LinkManager clients

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