GPU TPC: Fix TPC clusterizer qMax cut

[davidrohr]

Checking stored CTFs, I saw that we have clusters with qMax = 3, while we process with cfQMaxCutoff = 3, which should cut away qMax <= 3. I ran some local tests processing raw data, and I see that indeed the clusterizer produces clusters with qMax = 3, while the cut seems to be correct:

AliceO2/GPU/GPUTracking/TPCClusterFinder/GPUTPCCFPeakFinder.cxx

Line 45 in f76f1a7

bool belowThreshold = (q <= calib.tpc.cfQMaxCutoff);

Perhaps this is related to charge splitting between clusters? In any case, this PR fixes it by having a posterior cut on the qMax when the cluster is stored.

@fweig : Could you have a look and comment what happens in the clusterizer?

[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-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1