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
This PR creates a non-reproducability problem in HLT. It is present since when this PR was
accepted into the IB (09-11-0200). It is cured when keeping the PR but ONLY switching back
to using the legacy error (ie, flip "flase" to "true" in the "?" above).

More info:

The reproducability test compares running the full HLT menu with all paths at the
same time in the same cmsRun job, with running just one HLT path at a time, each
in a separate cmsRun job. Each trigger path should accept the same (number of) 
events in the two cases. However, with this PR, this is no longer the case for two of
the tracking based HLT baths.

Could the expert/PR-submitters please check the nonLegacy branch, whether it has some sort
of "internal memory" where its result depends on what has been done already earlier in the
event processing?
Cleary this non-reproducability issue is a problem for any HLT-based study... :((