reset_timeout_detection() is already called at end of NEXT_PAYLOAD
handler to properly re-init the timer on every new execution.
Remove the additional call in synchronization_lock() which prevents
proper timeout on targets that do a lot of hprintf().
Also remove extra call in synchronization_lock_timeout_found() which
really just seems to be a duplicate with no observable effect.
To reproduce, run a harness that uses hprintf() in infinite loop. It
will take longer due to execute due to userland overhead but should
eventually return with aux_buffer/runtime similar to configured timeout.
