fix in FT0 digitization (time wrt BC)

[noferini]

FT0 digitization: moving mIntRecord.getTimeOffsetWrtBC() when caching digit in order to use the current (and correct) collision time

Two plots from TOF QC after this commit is included... TOF-FT0 correlation recovered

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1

[afurs]

we also use hit_time here (hit_time > 150), w/o coll time

[afurs]

Hello @noferini I suggest to postpone this commit until we check some other cases (marked in the code) where hit_time is used w/o coll time.

[noferini]

Hi @afurs ,
It Is fine.
Then I close the pr.
Cheers
Francesco

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[noferini]

Thanks
Francesco