Infra proxy client details page view

[vinay033]

For #1544, the only functionality to add is the ability to see the public key for each client. This enables the user to compare the public key on the server to one on disk to get a sense if the key pair is correct when troubleshooting authentication problems.

Because we're not adding any bifrost permission UI, like on the other pages the permissions tab from Chef Manage is out of scope.

Because we aren't adding "write" support today, the "reset key" flow is also out of scope. That would be done as part of #3384.

Below is the current UI from Chef Manage

"validator clients" have special permissions. their original purpose was to be able to only create new nodes but limit access to any other actions. Today we recommend users use "validator-less bootstrapping" which uses their user key to create the nodes instead. This avoids having to manage everyone in the organization having a copy of the same validator keypair on disk. Chef Manage indicates which key pairs are validator key pairs with additional text, as seen below. This value is returned as part of the GET for an individual client, not for all the clients, which is why it is only displayed on the detail page and not the list of clients.

https://docs.chef.io/api_chef_server/#get-11