Client token selection logic ignores Scitokens JWTs

[brianhlin]

Pelican Version:

7.14.1

Pelican Service:

• Client
• Plugin
• Registry
• Director
• Origin
• Cache
• Other (please give the detail)

Describe the bug
When Pelican is presented with multiple SciTokens, it cannot find the correct one because it deems non-WLCG tokens as unacceptable (https://github.com/PelicanPlatform/pelican/blob/main/client/acquire_token.go#L441-L444). The client may get lucky picking the correct token if it's named scitokens.use or in the absence of a scitokens.use, whatever token comes first in the filepath.Walk (https://github.com/PelicanPlatform/pelican/blob/main/client/acquire_token.go#L201).

To Reproduce
Generate a JWT with ver: "scitokens:2.0" and pass it to pelican object get -d -t <path to token>. You should always get a warning:

Using provided token even though it does not appear to be acceptable to perform transfer

Expected behavior
I expect Pelican to be able to perform the same acceptability checks (e.g., scope + path comparisons) for SciTokens as it does for WLCG tokens

[brianhlin]

Once this is merged for 7.16, I'd like the fix cherry picked back into a 7.15 for a patch release