Remove ToT thresholds for ITk
In ATLITKSW-166 it is observed that ToT threshold cuts applied in master for ITk cause divergences from the digitization results we saw in 21.9
These changes were not implemented in discussion with the ITk experts, so it is not clear what the reason for the values chosen - @stsuno could you give some information perhaps?
At least While we are establishing our baseline comparisons with 21.9 we would like to remove these cuts. Appropriate values can be re-discussed layer once we have seen that the baseline checks give reasonable agreement.
As a further point, I find the way the PixelConfigCondAlg is designed, with different member info vectors for different run periods to be a bit over complicated. Why can this not just have a member info for all the parameters that gets simply configured differently based on which run, rather than needing a single configuration supporting all runs? This should be revisited later.