Add new TransferAd Atributes for parts of TransferUrl

[williamnswanson]

Pelican Service:

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

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Parsing the different parts of the raw TransferUrl directly from the TrasnferAd is tricky to do in Elasticsearch or downstream from it, and we miss out on information that is known to the Client and/or Director at runtime such as which part of the path is the Namespace Prefix vs what is only relevant for the object store.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Could we add extra attributes into the TrasnferAds from the split up parts of the whole?
-Token file name (if specified in the TransferUrl)
-Schema ("pelican" / "osdf")
-Federation (Hostname / discoveryUrl that the client attempts to reach)
-Pelican Path (Prefix + path, for what the client asks for, before getting results back from the Director)
-Prefix (Which prefix the Director says the Pelican Path is for, filled in after client hears back)
-Origin / Objectstore subpath (Rest of the Pelican Path)

Linked Jira ticket: https://opensciencegrid.atlassian.net/browse/OPS-482