Update tracker alignment for 2021 realistic scenario

[christopheralanwest]

PR description:

The global tag queues for the phase1_2021_realistic scenario had to be branched to support the different needs of the Run-3 LHCC studies and CMSSW development. This PR introduces an updated tracker alignment [1] and a purely technical payload [2]. It re-synchronizes auto:phase1_2021_realistic with the GT used for the Run-3 studies, 106X_mcRun3_2021_realistic_v3.

It would be useful to have this PR merged to avoid spurious differences in comparison tests in future PRs that affect phase1_2021_realistic conditions, for example, the eventual 10_6_X backport of #27644.

GT diff with respect to current autoCond:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_v8/106X_upgrade2021_realistic_v9

GT diff with respect to GT for Run-3 studies:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun3_2021_realistic_v3/106X_upgrade2021_realistic_v9

The tag difference above corresponds to payloads that were introduced by PR #27203 and ignored for Run-3 scenarios in a subsequent commit to that PR.

[1] https://indico.cern.ch/event/831067/contributions/3485251/attachments/1871918/3080764/Run3Alignment_AlcaDB017_AdeWit.pdf
[2] https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_v8/106X_upgrade2021_realistic_v9

PR validation:

Payload validation can be found in [1] and [2]. In addition, runTheMatrix.py -l 11624.0 was executed as a technical test.

[1] https://indico.cern.ch/event/831067/contributions/3485251/attachments/1871918/3080764/Run3Alignment_AlcaDB017_AdeWit.pdf
[2] https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_v8/106X_upgrade2021_realistic_v9

if this PR is a backport please specify the original PR:

This is not a backport per se but PR #27441 introduced into 11_0_X the tracker alignment payload used in this PR. But it introduced other changes as well; only the changes needed for consistency with existing 10_6_X workflows are used here.

[cmsbuild]

A new Pull Request was created by @christopheralanwest for CMSSW_10_6_X.

It involves the following packages:

Configuration/AlCa

@christopheralanwest, @tocheng, @cmsbuild, @franzoni, @tlampen, @pohsun can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @mmusich, @tocheng this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

[christopheralanwest]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/1729/console Started: 2019/07/31 05:19

[cmsbuild]

+1
Tested at: 7c34616
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-25eeed/1729/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 953 differences found in the comparisons
• DQMHistoTests: Total files compared: 33
• DQMHistoTests: Total histograms compared: 3208248
• DQMHistoTests: Total failures: 867
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3207047
• DQMHistoTests: Total skipped: 334
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
• Checked 137 log files, 14 edm output root files, 33 DQM output files

[christopheralanwest]

+1

• Changes only in tracking-related quantities in 2021 workflow 11624.0, as expected
• Tracker alignment payload validated locally and already included in GT used in master branch.

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

[kpedro88]

+1