Set phase1 track algorithms properly

[makortel]

This PR sets the phase1-specific track algos properly in the Phase1PU70 and Phase1PU140 tracking configurations.

Following migrations are included (should cover everything except tracking validation and DQM):

• The use of track algos in PF is migrated. The initial guess is to treat the new quadruplet iterations as the (current) triplet iterations. @bachtis @arizzi @gpetruc feel free to double-check.
• LhcTrackAnalyzer is supposedly not used, and is thus modified to throw if it encounters a track with phase1-specific algo, as agreed with alignment (@tlampen @mschrode).
• AdHocNtupler was straightforward to migrate.

Tracking validation and DQM will be migrated separately (need the phase1 era for that, see e.g. #12806).

Tested in 8_0_0_pre4, no changes expected in Run2 workflows.

@rovere @VinInn

[cmsbuild]

A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_8_0_X.

It involves the following packages:

Alignment/HIPAlignmentAlgorithm
PhysicsTools/UtilAlgos
RecoParticleFlow/PFTracking
RecoTracker/IterativeTracking

@diguida, @cvuosalo, @cerminar, @monttj, @cmsbuild, @franzoni, @slava77, @vadler, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @mmarionncern, @GiacomoSguazzoni, @tocheng, @VinInn, @mschrode, @rovere, @cerati, @gpetruc, @istaslis, @lgray, @dgulhan, @bachtis this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

Following commands in first line of a comment are recognized

• +1|approve[d]|sign[ed]: L1/L2's to approve it
• -1|reject[ed]: L1/L2's to reject it
• assign <category>[,<category>[,...]]: L1/L2's to request signatures from other categories
• unassign <category>[,<category>[,...]]: L1/L2's to remove signatures from other categories
• hold: L1/all L2's/release manager to mark it as on hold
• unhold: L1/user who put this PR on hold
• merge: L1/release managers to merge this request
• [@cmsbuild,] please test: L1/L2 and selected users to start jenkins tests
• [@cmsbuild,] please test with cms-sw/cmsdist#<PR>: L1/L2 and selected users to start jenkins tests using externals from cmsdist

[diguida]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/10367/console

[cmsbuild]

+1
Tested at: 971a1a0
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12834/10367/summary.html

[mmusich]

+1
minimal change in LhcTrackAnalyzer pending overall re-thinking of alignment package for phase-I

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12834/10367/summary.html

[slava77]

+1

for #12834 971a1a0

• changes in the code are as described
• jenkins tests pass and comparisons with the baseline show no differences (phase1 workflows were not tested)