commander: unify offboard timeouts

The implementation before this change had two timeouts, a hard-coded
timeout of 0.5 seconds as well as a by param configurable timeout with
certain failsafe actions set.

This change aims to fix two problems:
1. The hard-coded offboard timeout can be triggered easily with sped up
   lockstep simulation. Since i t is hard-coded it can't be adapted to
   the speed factor.
2. The offboard signal can time out but no action will be taken just
   yet. This means we end up in an in-between stage where no warning or
   failsafe action has happened yet, even though certain flags are set
   to a timeout state.

This patch aims to fix this by unifying the two timeouts to the existing
configurable param. The convoluted double timeout logic is replaced by a
simple hysteresis.

For anyone that has previously not changed the default timeout param (0),
the param will now be changed to 0.5 seconds which reflects the
previously hardcoded time. For anyone with a specific timeout
configured, the behaviour should remain the same.

Also, going forward, timeouts lower than 0.5 seconds should be possible.

msg/vehicle_status_flags.msg

@@ -26,7 +26,6 @@ bool circuit_breaker_vtol_fw_arming_check 	# set to true if for VTOLs arming in
 bool offboard_control_signal_found_once
 bool offboard_control_signal_lost
 bool offboard_control_set_by_command                # true if the offboard mode was set by a mavlink command and should not be overridden by RC
-bool offboard_control_loss_timeout                # true if offboard is lost for a certain amount of time
 
 bool rc_signal_found_once
 bool rc_input_blocked                                # set if RC input should be ignored temporarily