mavlink_messages: refactor to use vehicle_trajectory_waypoint instead of trajectory_waypoint message

points of the trajectory

nuttx_omnibus-f4sd_default: disable bl_update, wind_estimator, gnd_att_control, gnd_pos_control to save flash

avoidance

avoidance

trajectory_waypoint and trajectory_waypoint_desired

obstacle avoidance waypoints

in the pos_control and not coming from navigator. Refactor method
update_avoidance_waypoint_desired since all waypoints have the same type

code

if obstacle avoidance is running

to eliminate duplicated code

trajectory_waypoint

waypoint to the obstacle avoidance module

obstacle avoidance

waypoint

obstacle avoidance

obstacle avoidance module

uORB trajectory_waypoint as input path to a obstacle avoidance node

trajectory_waypoint or trajectory_bezier depending on the mav trajectory
representation type

- reorders operations, such that the most expensive one (orb_copy) is done
  only when really needed.
- corner case: when the topic was not advertised yet, orb_stat() would fail
  and then update() was called, which succeeds for the first advertisement.
  In that case the timestamp was incorrectly set to 0 and true was
  returned.
  The next call would again return true, because the timestamp was updated,
  but the topic data was still the same.

Reduces CPU load by ~2% on a Pixracer.

This is a more generic solution for 532a9704, and also enables it for
vehicle_command_ack's.

In addition it avoids using a timestamp for subscription update checking,
because it does not work well together with orb queuing.