WMAgent: Forgotten tweak for WorkQueueManager to use production Rucio for data discovery

[todor-ivanov]

Impact of the bug
WMAgent

Describe the bug
While testing the new deployment method for WMAgent in preproduction, people have reported a missing tweak for the WorkQueueManager component, which was supposed to switch the component to use production Rucio server for data discovery. As explained here: this is needed because we do not have the full information for all the data in Rucio integration server, so this blocks a big portion of our validation workflows which cannot find their input data.

The needed change is as follows:

• At $WMA_CONFIG_DIR/config.py

  • config.WorkQueueManager.rucioUrl = 'http://cms-rucio-int.cern.ch' --> config.WorkQueueManager.rucioUrl = 'http://cms-rucio.cern.ch'
  • config.WorkQueueManager.rucioAuthUrl = 'https://cms-rucio-auth-int.cern.ch' --> config.WorkQueueManager.rucioAuthUrl = 'https://cms-rucio-auth.cern.ch'

• At $RUCIO_HOME/rucio.cfg

  • 'http://cms-rucio-int.cern.ch' --> 'http://cms-rucio.cern.ch'
  • 'https://cms-rucio-auth-int.cern.ch' --> 'https://cms-rucio-auth.cern.ch'

How to reproduce it
run any agent in with a team name starting with testbed-*.
Expected behavior
To have the tweak in place for testbed agents

Additional context and error message
The issue: #11945 depends on the resolution of the current one, which makes it a chained dependency for the WMAgent new deployment model meta-issue: #11314