[12.6.X] Fix warning message about PixelCPEFast in TkTransientTrackingRecHitBuilderESProducer

[mmusich]

backport of #40170

PR description:

This PR is a follow-up to #40003, which added the TransientTrackingRechitBuilder flavour for PixelCPEFast.
In that PR a new warning was emitted from TkTransientTrackingRecHitBuilderESProducer in order to warn the user that track angles will not be used, but since that was implemented in the constructor or the class, the message ended up being emitted every time the TransientTrackingRecHitBuilder_cfi was loaded, leading to the misleading message that PixelCPEFast was used in the track fit, even when in fact it was not (logs from recent IB relvals show that the message is present in each one of them, see e.g. wf 1.0 or wf 250408.0 ).
This PR fixes the problem by moving the LogWarning from the class constructor to the produce method, such that it is emitted only if the ES products are actually consumed by the downstream modules.
I profit of this PR (in commit 6bcc614) to automatically supply a service needed in case of the PixelCPEFast choice in tracker alignment common refitting sequence.

PR validation:

Tested with this branch that the spurious messages in relvals are removed.

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Verbatim backport of #40170.

[mmusich]

type tracking, bug-fix

[cmsbuild]

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_6_X.

It involves the following packages:

• Alignment/CommonAlignment (alca)
• RecoTracker/TransientTrackingRecHit (reconstruction)

@malbouis, @yuanchao, @ChrisMisan, @clacaputo, @cmsbuild, @saumyaphor4252, @tvami, @mandrenguyen, @francescobrivio can you please review it and eventually sign? Thanks.
@pakhotin, @VourMa, @adewit, @felicepantaleo, @GiacomoSguazzoni, @JanFSchulte, @tocheng, @VinInn, @missirol, @rovere, @tlampen, @gpetruc, @mmusich, @mtosi, @dgulhan this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

• Backported from Fix warning message about PixelCPEFast in TkTransientTrackingRecHitBuilderESProducer #40170

[mmusich]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3d4d8c/29319/summary.html
COMMIT: 3575332
CMSSW: CMSSW_12_6_X_2022-11-29-1100/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/40171/29319/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• No significant changes to the logs found
• Reco comparison results: 3 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3416693
• DQMHistoTests: Total failures: 3
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3416668
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 206 log files, 48 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[tvami]

+alca

[mmusich]

urgent

• certainly desireable fix for 12.6.0.

[mandrenguyen]

+reconstruction

[cmsbuild]

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

[perrotta]

+1