remove L1T legacy dependencies from pixel and strip DQM clients [15_0_X]

[mmusich]

backport of #47508

PR description:

This is a follow-up to #46716 and fixes a couple of leftovers in the Pixel and SiStrip DQM clients that are crashing now after the deletion of legacy L1T records at https://its.cern.ch/jira/browse/CMSALCAFAST-94 with:

----- Begin Fatal Exception 05-Mar-2025 10:36:43 CET-----------------------
An exception of category 'NoRecord' occurred while
   [0] Processing  Event run: 387552 lumi: 1 event: 350 stream: 0
   [1] Running path 'p'
   [2] Calling method for module L1GlobalTriggerRawToDigi/'gtDigis'
Exception Message:
No "L1MuTriggerScalesRcd" record found in the EventSetup.

 Please add an ESSource or ESProducer that delivers such a record.
----- End Fatal Exception -------------------------------------------------

This is circumvented by using where appropriate the stage2L1Trigger modifier.

PR validation:

setenv CMS_PATH "/cvmfs/cms-ib.cern.ch"
setenv SITECONFIG_PATH "/cvmfs/cms-ib.cern.ch/SITECONF/local"
cd DQM/Integration/python/clients
mkdir upload
cmsRun sistrip_dqm_sourceclient-live_cfg.py unitTest=True
cmsRun pixel_dqm_sourceclient-live_cfg.py unitTest=True runkey=cosmic_run

runs fine in this branch.

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:

Backport of #47508 to CMSSW_15_0_X for 2025 data-taking operations.

[mmusich]

type bug-fix

[cmsbuild]

A new Pull Request was created by @mmusich for CMSSW_15_0_X.

It involves the following packages:

• DQM/Integration (dqm)

@antoniovagnerini, @cmsbuild, @rseidita can you please review it and eventually sign? Thanks.
@batinkov, @francescobrivio, @threus this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

• Backported from remove L1T legacy dependencies from pixel and strip online DQM clients #47508

[cmsbuild]

cms-bot internal usage

[mmusich]

@cmsbuild, please test

[cmsbuild]

+1

Size: This PR adds an extra 28KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ffe8aa/44817/summary.html
COMMIT: ed58b5e
CMSSW: CMSSW_15_0_X_2025-03-05-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/47510/44817/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: 356 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 4018889
• DQMHistoTests: Total failures: 5854
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 4013015
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 218 log files, 189 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[antoniovagnerini]

+dqm

• spurious differences seen from unstable WF 12834.7 (open issue spurious differences in outputs of Run-3 wfs *.7 #39803 )
• spurious differences from unstable WF 29834.999(open issue Non-reproducibility in TrackerPhase2OTL1Track #47071)

[cmsbuild]

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

[mandrenguyen]

+1