Reset ITS tracks ROF counters if not tracks found

[shahor02]

@ChSonnabend this should fixe the crash you reported, thanks!

[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

[ChSonnabend]

Tagging also @ehellbar
Thanks for the fix @shahor02

[f3sch]

Can I ask what the setup was, seems a bit fringe that this then leads to a crash somewhere else?

[shahor02]

Here is the reproducer from @ChSonnabend and @ehellbar . The ROFs vector for tracks is created as a copy of the input clusters vector then filled with the tracks counters. But this is done if at least 1 ITS track is found. If not (for whatever reason), the ROF vector will preserve the cluster counters pretending these are tracks. Then, the downstream consumers of the ITS tracks crash.
workflow.sh.gz

[f3sch]

indeed makes sense, thanks for fixing and sorry for introducing this regression.