timestamp diagnostics must take into account time_offset

[procopiostein]

in our setup we have a big time offset due to delay in communications using the USB interface. because of that, the diagnostics fails because the timestamp delay is too big wrt the expected frequency.
with the current fix, the diagnostic_updater take into account the time_offset parameter.

[mintar]

Thanks! I've just tested your PR and it works as advertised.

The only thing that doesn't work is when you update the time_offset param using dynamic reconfigure after the node has started up, the TimeStampStatusParam won't be updated, but there seems to be no straightforward way to do that using the diagnostics API, so let's leave that for now.

Thanks again!

[procopiostein]

thank you!

[procopiostein]

do you expect to create a release of the last changes anytime soon? thanks!

[mintar]

Done!

[procopiostein]

thanks a lot!