remove module siPixelQualityESProducer from HLT cff files

The ESProducer siPixelQualityESProducer can be removed from
the cff fragments of the HLT configurations, as it is provided by the cff file

Configuration.StandardSequences.FrontierConditions_GlobalTag_cff

This avoids picking up the version of siPixelQualityESProducer defined in ConfDB
when a command like the following is used.

cmsDriver.py step2 --conditions 130X_mcRun3_2023_realistic_relvals2023D_v1 \
--datatier GEN-SIM-DIGI-RAW --era Run3_2023 --eventcontent FEVTDEBUGHLT \
--filein "dbs:/RelValTTbar_14TeV/CMSSW_13_0_11-130X_mcRun3_2023_realistic_relvals2023D_v1_RV204-v1/GEN-SIM" \
--fileout "file:step2.root" --geometry DB:Extended --nThreads 8 --no_exec --number 1 \
--pileup 2023_Fills_8807_8901_ProjectedPileup_PoissonOOTPU \
--pileup_input das:/RelValMinBias_14TeV/CMSSW_13_0_11-130X_mcRun3_2023_realistic_relvals2023D_v1_RV204-v1/GEN-SIM \
--python_filename step_2_cfg.py --step DIGI:pdigi_valid,L1,DIGI2RAW,HLT:run3:/dev/CMSSW_13_0_0/GRun/V151

Using HLT:[db]:[config] (as opposed to HLT:[menuKeyword], e.g. HLT:GRun)
leads to a call to the function loadHltConfiguration
after the process has loaded FrontierConditions_GlobalTag_cff,
thus overwriting the ESProducer from the latter cff with
the one defined in the HLT configuration as taken from ConfDB.
For details on a concrete use case, see

https://its.cern.ch/jira/browse/PDMVRELVALS-204

HLTrigger/Configuration/python/Tools/confdb.py

@@ -877,6 +877,7 @@ def buildOptions(self):
       self.options['esmodules'].append( "-ZdcGeometryFromDBEP" )
       self.options['esmodules'].append( "-XMLFromDBSource" )
       self.options['esmodules'].append( "-sistripconn" )
+      self.options['esmodules'].append( "-siPixelQualityESProducer" )
 
       self.options['services'].append( "-MessageLogger" )