add UiSettings client to action and alert executor's services parameter

[pmuellr]

The services parameter for actions and alerts currently only provides access to callCluster and savedObjectsClient.

kibana/x-pack/legacy/plugins/alerting/server/types.ts

Lines 19 to 22 in 0d19b38

	export interface Services {
	callCluster(path: string, opts: any): Promise<any>;
	savedObjectsClient: SavedObjectsClientContract;
	}

kibana/x-pack/legacy/plugins/actions/server/types.ts

Lines 17 to 20 in 0d19b38

	export interface Services {
	callCluster(path: string, opts: any): Promise<any>;
	savedObjectsClient: SavedObjectsClientContract;
	}

@chrisronline has requested access to the UI Settings client as well. He's currently stitching one together himself, with code copied from:

kibana/src/legacy/ui/ui_settings/ui_settings_service_factory.ts

Lines 31 to 36 in 0d19b38

	export function uiSettingsServiceFactory(
	server: Legacy.Server,
	options: UiSettingsServiceFactoryOptions
	): IUiSettingsClient {
	return server.newPlatform.__internals.uiSettings.asScopedToClient(options.savedObjectsClient);
	}

Copying these services in manually doesn't seem like it's going to scale, if we get a bunch more. Not quite sure what the best approach to avoid doing that might be.

Adding one more though isn't a huge issue.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[ymao1]

Closing in favor of #64588