Create API keys with metadata

[thomheymann]

Resolves: #100534
Resolves: #93820

Summary

Added the ability to create API Keys with metadata.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[legrego]

Thanks for putting this together so quickly!

A couple of additional comments:

1. Can we update the type definitions for both CreateAPIKeyParams and GrantAPIKeyParams within the server-side api key service to allow for metadata to be provided? This is part of the plugin's public contract that is consumed elsewhere, so it'd be good to record that we do in fact support metadata:
   

   kibana/x-pack/plugins/security/server/authentication/api_keys/api_keys.ts

   Lines 29 to 41 in 69f013e

   	export interface CreateAPIKeyParams {
   	name: string;
   	role_descriptors: Record<string, any>;
   	expiration?: string;
   	}
   	interface GrantAPIKeyParams {
   	api_key: CreateAPIKeyParams;
   	grant_type: 'password' | 'access_token';
   	username?: string;
   	password?: string;
   	access_token?: string;
   	}

2. Can we add an API test to ensure that we can pass metadata through successfully?:
   

   kibana/x-pack/test/api_integration/apis/security/api_keys.ts

   Line 29 in 69f013e

   describe('POST /internal/security/api_key', () => {

3. If you're up for it, we could update the documentation screenshot to include the new metadata toggle:
   https://github.com/elastic/kibana/blob/69f013e2fb64544bc9d16d3fe9f4ec6c14ed9c11/docs/user/security/api-keys/images/create-api-key.png

[bytebilly]

Great work @thomheymann! LGTM once all comments are resolved 👍
Should we update documentation at https://www.elastic.co/guide/en/kibana/current/api-keys.html#create-api-key too?

[legrego]

LGTM!

[legrego]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 1001c5b
• Storybooks Preview
• Documentation Changes

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
security	765.0KB	767.0KB	+2.0KB

Unknown metric groups

References to deprecated APIs

id	before	after	diff
infra	256	146	-110
lens	67	45	-22
licensing	18	15	-3
lists	239	236	-3
ml	121	115	-6
stackAlerts	101	95	-6
total			-150

History

• 💚 Build #127653 succeeded 1803c50
• 💚 Build #127405 succeeded f6bddae

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.