OA: interface update

[mrivi]

• Add the waypoint type (mavlink command associated with the waypoint) to the points in the OA interface
• refactor the check on the z progress of the mission

[dagar]

Did you see the CI failures? http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-SITL_tests/detail/PR-12349/1/pipeline

../../src/lib/FlightTasks/tasks/Utility/ObstacleAvoidance.cpp:55:1: error: narrowing conversion of '255' from 'int' to 'bool' inside { } [-Werror=narrowing]

 };

 ^

[dagar]

SITL MC avoidance as well.

http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-SITL_tests/detail/PR-12349/1/pipeline

[mrivi]

@dagar We cannot merge this one until there is a mavros update and consequent CI update. Problem is that TRAJECTORY_REPRESENTATION_WAYPOINT changed so the mavlink receiver is dropping all the messages coming from ROS because the definition don't match. It isn't an extention of the message but a proper change since it's still marked WIP in mavlink.

Also updating the mavlink submodule on its own will break the avoidance CI.

[bkueng]

Why is this needed?