[DOCS] Add configuration details to connector APIs

[lcawl]

The Action and connector APIs currently do not contain the details necessary to fill in the config and params objects. Instead, they link to Connectors docs.

Rather than expecting users to patch together that information, however, there seems to be no reason why we can't move that level of detail into the API pages.

In particular, we'd want to augment the create connector API, update connector API, and run connector API with details for all of the following connectors:

• D3 Security [DOCS] Move preconfigured D3 Security connector details #166112
• Email: [DOCS] Move preconfigured email connector details  #165181
• GenAI [Security solution] Generative AI Connector API specification #158423, [DOCS] Move preconfigured generative AI connector details #165418
• IBM resilient
• Index [DOCS] Add Jira and index connector details to create connector API #133347, [DOCS] Add Jira and index connector details to update connector API #133692, [DOCS] Add index connector actions to run connector API #134538
• Jira [DOCS] Add Jira and index connector details to create connector API #133347, [DOCS] Add Jira and index connector details to update connector API #133692, [DOCS] Add jira connector details to run connector API #134622
• Microsoft teams: [DOCS] Move preconfigured Microsoft Teams connector details #166119
• OpsGenie
• PagerDuty: [DOCS] Move preconfigured PagerDuty connector details #165361
• Server log [DOCS] Add server log connector details to connector APIs #134409
• ServiceNow ITSM
• ServiceNow SecOps
• ServiceNow ITOM
• Swimlane
• Slack [RAM] Docs for slack improvements #153885
• Tines: config, secrets [DOCS] Move preconfigured Tines connector details #166217
• Torq [DOCS] Move preconfigured Torq connector details #166218
• Webhook: config, secrets [OAS] Add Webhook connector configuration details #163899
• Webhook Case Management
• xMatters: [DOCS] Move preconfigured xMatters connector details #165923

The params that you can specify when you run a connector likewise might be incomplete: _execute.yaml

• run_connector_params_documents.yaml
• run_connector_params_level_message.yaml
• run_connector_subaction_addevent.yaml
• run_connector_subaction_closealert.yaml
• run_connector_subaction_createalert.yaml
• run_connector_subaction_fieldsbyissuetype.yaml
• run_connector_subaction_getchoices.yaml
• run_connector_subaction_getfields.yaml
• run_connector_subaction_getincident.yaml
• run_connector_subaction_issue.yaml
• run_connector_subaction_issues.yaml
• run_connector_subaction_issuetypes.yaml
• run_connector_subaction_pushtoservice.yaml
• getChannels, postMessage subactions per https://github.com/elastic/kibana/blob/main/x-pack/plugins/stack_connectors/common/slack_api/schema.ts
• ...?

[elasticmachine]

Pinging @elastic/kibana-docs (Team:Docs)

[lcawl]

Per discussion with @shanisagiv1 the most important connectors to get fully documented are email, slack, and server log. I believe the only pieces left to do in the specification are the execution actions. If a good publishing method for the API specifications is not imminent, those would be the connectors to consider manually adding to the old API docs as well.

[lcawl]

Since the configuration details are now complete, I've created #167931 to follow up on the missing run connector API details.