Cluster3DPCACalculator internally has been coded such that it also
computes timing information for the hits associated to the passed
clusters. Unfortunately this procedure was overwriting the newly
implemented method to compute timing for HGCAL clusters. HGCAL seems to
be the only left customer of this code. A flag has been added to disable
the assignment of timing to the cluster, not to disable the timing
computation. We are still in the process of defining where and how to
properly associate a timing to (which) cluster, so this solution can be
considered as temporary.