During tests, if the airframe was configured to be an 'X' type
we showed just 'X' on the airframe type. It's correct but a
single letter - specially an X - made users think that it was
a error code, not the airframe name. So, because of that, also
show the vehicle type - a wrong value, but elucidative for users.
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

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.

This way we don't need macro-magic to deal with
different operating systems and compilers.
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

Removed incorrect Vehicle.altitudeWGS84

Plumb through initial object mode on Vehicle

Also additional major Mission usability changes

Added conditional statement to disable the virtualTabletJoystick output if a real joystick is connected and enabled. Without this, two different sets of values would be sent and would appear highly sporadic.