Possible bug: use of hltScoutingEra_Run3_2024 instead of 2025

[silviodonato]

Impact of the bug
Likely none, as 2024 seems identical to https://github.com/cms-sw/cmssw/blob/master/Configuration/DataProcessing/python/RecoTLR.py#L97-L100

Describe the bug
@mtosi noticed that in https://github.com/dmwm/T0/blob/master/etc/ProdOfflineConfiguration.py#L128
we are using hltScoutingEra_Run3_2024 instead of hltScoutingEra_Run3_2025.
Note that Configuration/DataProcessing/python/Impl/hltScoutingEra_Run3_2025.py was added by @srimanob with #47536, so most likely we should indeed use hltScoutingEra_Run3_2025,
similarly to what was done by @LinaresToine with #5050 for pp

cc @patinkaew

[patinkaew]

Hi all,

I think there shouldn't be any impact because Run3_2025 is based on Run3_2024 era modifier [1] and there is no scouting-related modifier added for 2025 as far as I'm aware of. However, to avoid confusion, it might be good to change to 2025 scenario.

Best,
Patin

[1] https://github.com/cms-sw/cmssw/blob/master/Configuration/Eras/python/Era_Run3_2025_cff.py#L10

[silviodonato]

This change was done in #5072
and then reverted (by mistake ?) with #5071

[LinaresToine]

Thanks @silviodonato and apologies for this. The configuration file was updated.