If a log with multiple (dis)arming events was replayed, multiple logs were
created. This changes the replay to only create a single log.

-created a test base class to centralize redundant methods among the different tests
-added mission waypoint list topic listener (this also helps make sure the simulation is ready)
-check number of mission waypoints in FCU against mission
-increase time for mavros topics to be ready from 30 to 60 seconds
-reduce position check loop rates
-clean up logging
-support QGC plan for mission file format, see #8619
-vehicle is an arg for mission test launch file, working toward other airframes
-Jenkins: fix vtol vehicle arg value
-get MAV_TYPE param and use FW radius for pure fixed-wing mission position check
-remove unused vehicle arg from test in multiple tests launch, clearing runtime warning

This brings in new ROI commands and general sync.

The calls have not been updated as the CI target has been.

This is temporary until there is a solution that works for adc and posix power modules

 - the SuperBlock already does this

The debug messages are too verbose to be run in a production vehicle and inherently were something that should only be run in SITL / debug sessions on hardware. Switching the flag to the PX4_DEBUG() macro does not only make this more explicit, but also saves a lot of flash space that otherwise was consumed by the strings.

This ensures that users do not accidentally enable this in an airborne system and saves flash space.

And also format file according to code style.