new phase1Pixel version

Phase1 Geometry from @alessia : FPIX+ is reflected instead of rotated as it was so far.

This as been presented here:
https://indico.cern.ch/event/342233/session/2/contribution/2/material/slides/0.pptx

This PR is modifying the 2017 dev scenario so this is transparent for any ongoing MC Prodcution for the TP- 

@venturia , @alessia : to test it (from gensim to DQM)  , you can use runThematrix 
runTheMatrix.py --what upgrade -l 10600 

or directly the cmsdriver commands : 

[1]: cmsDriver.py FourMuPt_1_200_cfi  --conditions auto:upgrade2017 -n 10 --eventcontent FEVTDEBUG --relval 10000,100 -s GEN,SIM --datatier GEN-SIM --beamspot Gauss --customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2017dev --geometry Extended2017dev,Extended2017devReco --magField 38T_PostLS1 
                                       
[2]: cmsDriver.py step2  --conditions auto:upgrade2017 -n 10 --eventcontent FEVTDEBUGHLT -s DIGI:pdigi_valid,L1,DIGI2RAW --datatier GEN-SIM-DIGI-RAW --customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2017dev --geometry Extended2017dev,Extended2017devReco --magField 38T_PostLS1
                                           
[3]: cmsDriver.py step3  --conditions auto:upgrade2017 -n 10 --eventcontent FEVTDEBUGHLT,DQM -s RAW2DIGI,L1Reco,RECO,VALIDATION,DQM --datatier GEN-SIM-RECO,DQMIO --customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2017dev --geometry Extended2017dev,Extended2017devReco --magField 38T_PostLS1
                                           
[4]: cmsDriver.py step4  --conditions auto:upgrade2017 --scenario pp -s HARVESTING:validationHarvesting+dqmHarvesting --filetype DQM --customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2017dev --geometry Extended2017dev,Extended2017devReco --mc  --magField 38T_PostLS1 -n 100