[9.0] Improve CI to include legacy adaptor

[Robin-Van-de-Merghel]

BEGINRELEASENOTES

*Integration Tests
FIX: Add in CI and in integration_test.py legacy adaptors.

ENDRELEASENOTES

[Robin-Van-de-Merghel]

Todo (here or in another PR): add doc to explain how it works + to show MacOS compatibility (OSX=true ./integration_tests.py ...)

[Robin-Van-de-Merghel]

Two bugs were found @chrisburr @chaen (discussed F2F with Christophe, told me to pin):

1. e3b1d68 in dirac-proxy-init.

If we have a group jetkins_users in VO Jenkins, but without VOMS, by doing dirac-proxy-init it will work in DIRAC (work meaning "there won't be an error raised") but our VO will secretly be the DIRAC VO. If we activate DiracX (purpose of this PR), it will lead to a 400 error because DiracX verifies that our VO corresponds to our group, which in this case is False.

In the commit, we can see that I changed a call of getVOMSVOForGroup to getVOForGroup, and this bit that was switched in getVOForGroup:

getVO() or gConfig.getValue(f"{gBaseRegistrySection}/Groups/{group}/VO", "")
# to
gConfig.getValue(f"{gBaseRegistrySection}/Groups/{group}/VO", "") or getVO()

2. d2f99c0 in setJobAttributes for Status.

In the past, while testing this function we did this:

res = jobStateUpdateClient.setJobStatusBulk(
            jobID,
            {
                str(datetime.datetime.utcnow() + datetime.timedelta(hours=1)): {
                    "Status": JobStatus.WAITING,
                    "MinorStatus": "MinorStatus",
                    "Source": "Unknown",
                },
            }
            False,
)

# ...

res = jobStateUpdateClient.setJobStatus(jobID, JobStatus.RUNNING)

# ...

assert res["Value"]["Status"] == JobStatus.RUNNING

The test is wrong: while doing setJobStatusBulk (at the top), we set a time 1 hour in the future, while in the setJobStatus we set it in the present. As I connected the JobStateUpdateClient to DiracX, this test failed because DiracX follows the right behaviour.

I did not fix setJobStatus because we use now DiracX.

[Robin-Van-de-Merghel]

Other fix: Now, if a service is set as "legacy adapted" in the CS but not set in the legacy client (diracxClient = future...), it will raise instantly an error.

(Before, only warn logs were emitted, and by default, a diset client were taken)