New strip cpe

Updates the strip rechit resolution parameterization.

Presented in the offline reco meeting here:
https://indico.cern.ch/event/330430/session/5/contribution/18/material/slides/0.pdf

The summary of the work, including pointers to previous presentations and code locations can be found at this tracker DPG meeting:
https://indico.cern.ch/event/305424/session/0/contribution/25/material/slides/0.pdf

In addition to a presentation on the impact on alignment:
https://indico.cern.ch/event/305425/session/0/contribution/17/material/slides/0.pdf
Nasty...
const-correctness ensures that cannot be explicit.
One possibility is that, via unknown mechanism such as memory corruption, useLegacyError, (or any of the other parameters), is modified.


The legacyError uses constants so it is not sensitive to memory corruption.

Said that, I do not believe much in memory corruption, still Valgrind is a must at this point...

@Martin-Grunewald, @mtosi : could you please set a reproducible example based on "concrete" cfg?
i.e. provide two cfg: one with all path, the other with just one of the path that shows discrepancy? thanks