Fix broken NO_SERIAL_LINK build

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.

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

- 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

Add the HeartbeatTimer class to track a single heartbeat for a single link.
For every new received heartbeat an instance of the class is created.
Every instance emits a signal if it timed out or the timer is restarted.
Each vehicle then decides based on all different signals which link is the
priority link.

This ensures no ports are being displayed to the user that are definitely unusable.

We were connecting to system peripherals before, which adds boot delay as QGC re-tries opening the port. We were also opening serial ports two times on Mac OS: Once as /dev/cu.usbmodem1 and once as /dev/tty.usbmodem1 - since the cu.usbmodem alias was already open, the 2nd opening always failed, leading to further boot delay.

Instead of hardcoded "QGroundContorl" strings

Prevent shutdown ordering crashes

No need to add dynamic MockLink comm links