3007 api key UI

[1ddo]

• Identified the issue which this PR solves.
• Read the CONTRIBUTING document.
• Code builds clean without any errors or warnings.
• Added appropriate tests for any new functionality.
• All new and existing tests passed.
• Added comments in the code, where necessary.
• Ran make check to catch common errors. Fixed any that came up.

Description:
Adds a page for API key creation and deletion. When a key is created, it can be viewed and copied only until the dialog is closed. After that, a new one must be created if lost.

Use the command make start EXPERIMENTAL=gql-api-keys to functionally test.

Which issue(s) this PR fixes:

Out of Scope:

Screenshots:

Describe any introduced user-facing changes:

Describe any introduced API changes:

Additional Info:

[Forfold]

A few things. When using the Create API Key dialog, I'm seeing the error:

useControlled.js:35 MUI: A component is changing the default value state of an uncontrolled Autocomplete after being initialized. To suppress this warning opt to use a controlled Autocomplete. 

After submitting when viewing the API key to copy, I get the error:

<p> cannot appear as a descendant of <p>.

Also, can we fix the following:

• Decrease the max-width on the copy API key dialog by a level
• Update "No Data Available" to "No Results"
• Match the whitespace for the header and the no results text

• Have list go to full width of card so there's no margin when hovering/selected:

• Center time text in list, or add a secondary <OtherActions /> for editing and deleting, to match other list pages:

• Format delete dialog with Cancel, Submit, and Title Case "Delete API Key":

• The transition throws an error when selecting/deselecting a key:

Failed prop type: Invalid prop `in` of type `object` supplied to `ForwardRef(Fade2)`, expected `boolean`.

[Forfold]

I can work on the above fixes ^

[Forfold]

Optimistic updates on creating and deleting would be nice, but it's looking good to go 👍