This was a real issue for long paths and not a flight safety issue for regular users, but could have been an issue for developers trying to use FTP on very deep nested file systems

Due to known input this was not a real issue, but bad style.

This was harmless but none the less is not good style and needs fixing.

Sadly, we cannot use std::array on NuttX

It causes problems because it includes px4_nodehandle.h which in turn
includes <functional>, and this is not available on NuttX

 - dataman clean exit code
 - unit test proper cleanup
 - add some level of simulated sensors for tests
 - delete unused test/standard_vtol

It doesn't make sense to reset the reached sequence, especially not to
false since it's an int.

We don't want to reset the current waypoint because this means that the
ground stations see a current waypoint of 0 if the current waypoint is
not updated e.g. when we're not in mission mode.

However, it is wrong to send 0 as the current waypoint because if we
switch back to mission mode, it will actually go to the last current
waypoint and not 0.

 - PX4_ASAN=1 enable address sanitizer (was MEMORY_DEBUG)
 - PX4_TSAN=1 enable thread santiizer
 - PX4_UBSAN=1 enable undefined behaviour santizier (some options off)