Fix mapping of MAV_STATE
Fix mapping of MAV_STATE

Previously, mavlink_vehicles was mapping the more specific mavlink MAV_STATE
enum to a more generic STATUS enum as follows:

MAV_STATE_UNINIT -> mavlink_vehicles::status::STANDBY
MAV_STATE_BOOT -> mavlink_vehicles::status::STANDBY
MAV_STATE_CALIBRATING -> mavlink_vehicles::status::STANDBY
MAV_STATE_ACTIVE -> mavlink_vehicles::status::ACTIVE
MAV_STATE_CRITICAL -> mavlink_vehicles::status::STANDBY
MAV_STATE_EMERGENCY -> mavlink_vehicles::status::STANDBY
MAV_STATE_POWEROFF -> mavlink_vehicles::status::STANDBY

This simplification has been placed taking in consideration only a specific use
case: determine whether the vehicle is already flying (ACTIVE) or not
(STANDBY). While testing It has been noted that the states STATE_CRITICAL and
STATE_EMERGENCY might also be set during flight, and so, those should also be
mapped to mavlink_vehicles::status::ACTIVE.

This is what this patch does:

MAV_STATE_UNINIT -> mavlink_vehicles::status::STANDBY
MAV_STATE_BOOT -> mavlink_vehicles::status::STANDBY
MAV_STATE_CALIBRATING -> mavlink_vehicles::status::STANDBY
MAV_STATE_ACTIVE -> mavlink_vehicles::status::ACTIVE
MAV_STATE_CRITICAL -> mavlink_vehicles::status::ACTIVE
MAV_STATE_EMERGENCY -> mavlink_vehicles::status::ACTIVE
MAV_STATE_POWEROFF -> mavlink_vehicles::status::STANDBY

Signed-off-by: Guilherme Campos Camargo <564b2b7fead5c6563c25bad017ee4ddcfee1ede9@intel.com>

guiccbr/mavlink-vehicles