Namespace UI

[CannonLock]

• Show namespace capabilities
• Show interaction between namespace and server capabilities

[CannonLock]

[CannonLock]

Closes #1724

[CannonLock]

New namespace card with the nested capabilities. Should give easy insight to what caches and origins provide what capabilities for this namespace.

[CannonLock]

Closes #1210

[h2zh]

New namespace card with the nested capabilities. Should give easy insight to what caches and origins provide what capabilities for this namespace.

There are multiple "issuer" showing up here. I think it'd be better to differentiate them here in case causing further confusion. Here are my two cents to avoid semantic overload:

1. Change "issuer" under "token generation" to another word, like "generator". Also change its occurrences everywhere else
2. Add tool-tip to "issuer" and "generator", explaining their difference in Pelican project. For example:

• Token Generator: a server that performs the technical task of creating the token
• Token Issuer: a server as a trusted authority that vouches for the authenticity of the token

Could you take a quick look and share your thoughts on the necessity of this change @jhiemstrawisc

Update: after talking to Justin, we decide to not include semantic change in this PR.