TPC: dEdx calculation class is extended

[tubagundem]

Standalone dEdx calculation class is extended:

• New subthreshold cluster treatment is added.
• Cluster mask is implemented to exclude single, edge, split and subthreshold clusters from dEdx calculation. Also an option to exclude sector boundaries from subthreshold cluster treatment is added.
• o2::gpu::GPUO2InterfaceRefit::fillSharedClustersAndOccupancyMap is added for the function RefitTrackAsGPU

[github-actions[bot]]

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-apass3 async-2023-pbpb-apass4 async-2023-pp-apass4 async-2024-pp-apass1 async-2022-pp-apass7 async-2024-pp-cpass0

[tubagundem]

I added two new parameters to limit minChargeTot and minChargeMax values when handling subthreshold clusters. Sometimes, the algorithm finds subthreshold clusters in high dEdx tracks, but the minimum charge is too high, indicating the cluster might be lost for another reason.

In the screenshot below, you can see the algorithm detects three subthreshold clusters for a high dEdx track, and both minChargeTot and minChargeMax values are too high. In this case, virtual charges should not be added to the track.

This is the debug output. Debug vectors are also filled when a cluster is skipped for any reason. In the cluster loop, the previous row index and sector index are updated to match the skipped cluster, so it is not counted as a subthreshold cluster.

[github-actions[bot]]

This PR did not have any update in the last 30 days. Is it still needed? Unless further action in will be closed in 5 days.