drv_hrt: allow time differences across timestamp wrap again

[MaEtUgR]

Solved Problem

Fixes #23378

Solution

reverting a small part of 4a55393

Changelog Entry

Bugfix: allow time differences across timestamp wrap again

Alternatives

We could check why these occur in the first place.

Test coverage

The SITL test procedure I used to reproduce the original issue passes again.

Context

#22881

[DronecodeBot]

This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/px4-sync-q-a-july-10-2024/39614/1

[katzfey]

This will break VOXL 2

[MaEtUgR]

@katzfey I'm aware and I really do not want to break the board support you contributed! That's also why this pr is a draft. Like I wrote here: #23378 (comment) it would be nice to avoid the additional overhead with this much used time critical inline function and behavioral side effects on all setups just because the microcontroller timestamps jump back on VOXL even though that's not supported by other components. All I'm saying is another solution to the time synchronization would be desired.

#23384 at least fixed the blocking problem that broke the PX4 main branch.

[katzfey]

Is the extra CPU load for this extra check quantified? If it is large we could just ifdef the code so that only VOXL 2 boards suffer the extra overhead.