Comprehensive debugging

[slaghuis]

This node has to be debugged with the new Tracker node, and the drone_mavsdk node. Lessons were learnt when developing the navigation stack, and it is assumed that this node has logic errors or at least vast improvement opportunity applying those leanings.

[slaghuis]

In Approach and Descending state the drone navigates relative to the landing target by increasing FLU velocity. As presented, the code determines the error to be corrected in the MAP frame which is ENU. This thing will fly away.
Amend code to read the positional error in the odom frame which is what we control when descending. Should I read the transform from landing_target to base_link. Surely this is the error that has to become 0;0 before descending?