On desktop (Ethernet connection), the ground unit pushes UDP directly, which makes the use of an actual "Link" not possible. Instead, I've moved all of Taisync support to a "manager" owned by QGCToolbox.
Added a Taisync settings with some basics already wired and running.

Three components for better testing

Prevent counter overflow

16 RC channels

Support parameters from multiple components

Support new ArduPilot bootloader PID/VIDs

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Us MAV_COMP_ID_AUTOPILOT1 instead of MAV_COMP_ID_MISSIONPLANNER

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Q_ENUMS is deprecated and should not be usued.
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Fixed the core MAVLink receiver. Among other things, it wasn't accounting for fragmented messages.
Fixed code that monitors messages received (and lost)
Added a section within the MAVLink panel to show the current status (for the current vehicle)
Remove some old, unused exposed interfaces

Back up further from end of file to handle more cases

ArduPilot ChibiOS support

Previously the first activeChanged signal got lost because it was not connected yet to the LinkInterface which resulted in a link incorrectly shown as inactive.

Show the link indicator in the tool bar if two or more links are connected and at least one of them is a high latency link.
Show in the link indicator if a link is inactive.

- Improve function names
- For notifications of an active link change only show the priority keyword if multiple links are connected
- Use QMap instead of QList for the HeartbeatTimers
- Style improvements
- Simplify sending the MAV_CMD_CONTROL_HIGH_LATENCY command