feat: Adding JWT support alongside X509 auth

[Robin-Van-de-Merghel]

Added BaseConnectedRequest to support multiple auth mecanism. Derived from it are two classes:

• TokenBasedRequest
• X509BasedRequest

You can use either of these.

The code still work as previously with a X509 authentification, using X509BasedRequest, see here

Later, we can transition to a TokenBasedRequest. For that, we'll need to replace the X509_USER_PROXY env variable with a JWT_USER or something similar.

[Robin-Van-de-Merghel]

I am still testing the code. Need changes.

[aldbr]

(You need to fix the conflicts with pilotTools)

[Robin-Van-de-Merghel]

Improved it so we can just change a parameter in sendMessage to support jwt and x509.

I would like a discussion about storing the JWT:

• an env with directly the encoded token
• an env with a path to the token (as for certs)
• a string parameter in the function, that sendMessage receives from RemoteLogger that himself has from the pilotConfig

For now I've chosen the first choice, tell me if you think it is right.

[Robin-Van-de-Merghel]

[Issue with python 2]

[Robin-Van-de-Merghel]

Is there other changes to do?

[Robin-Van-de-Merghel]

Better with a command than a function that retrieves the JWT. Uses dirac pilot-login <ref> <secret> defined in this PR of DiracX.

[Robin-Van-de-Merghel]

Needs an update to match DiracX's PR.

[Robin-Van-de-Merghel]

TODO: self.pilotStamp = os.environ.get("DIRAC_PILOT_STAMP", self.pp.pilotUUID)

[Robin-Van-de-Merghel]

Needs a small update to be up to date with the DiracX PR

[Robin-Van-de-Merghel]

Note: BaseRequest etc. isn't used yet for logs because it will be deprecated in the next PR.