Fast clusterhitfinder - on cluster split the charge value is not adjusted at pad boundary between the clusters

EDIT 2025-09-22: seems in fast clustering v2.0.8b it is fixed

EDIT 2025-03-25: the new version of fast clustering is out, to be investigated whether the issue is still present

EDIT 2023-12-30: after 76c0aadc the behavior changed, but it seems the fix is not 100% correct

---

Example: on the pad 15 the digits are present in both clusters, but the charge is not split.
The generated error is negligible as the charge on boundary is relatively small, but this probably should be fixed in the future - for consistency's sake (charge conservation).

For the reference the splitAdcHit method from TpcClustering.h is currently called only when clusters are separated on temporal boundary (timebins).