[DOCS] Consolidated rule status

[lcawl]

Relates to #136039

The documentation impact of this work is as follows:

• API documentation: The new next_run and last_run properties and deprecated execution_status properties are likely to affect API examples in:
  • create rule API N/A
  • find rules API [DOCS] Create open API specification for find rules #147061
  • get rules API [DOCS] Create open API specification for update/get/delete rule #147407
  • update rule API [DOCS] Create open API specification for update/get/delete rule #147407

For example:

• UI text: The meaning of the new statuses seems straight-forward enough that it doesn't require help text in the UI.

• Kibana documentation: If we keep the descriptions in https://www.elastic.co/guide/en/kibana/master/create-and-manage-rules.html#_rule_status, they'll need to be updated. Execution status also appears in the alerting troubleshooting page. Some screenshots might need to be updated if they show the old statuses (e.g. "OK" status in https://www.elastic.co/guide/en/kibana/master/create-and-manage-rules.html will change to something like "succeeded").

  • [DOCS] Refresh alerting troubleshooting  #147633
  • [ResponseOps] Automate screenshots for new rule statuses #147492

• Observability documentation: Affects screenshots that show status values. For example: https://www.elastic.co/guide/en/observability/current/view-observability-alerts.html, https://www.elastic.co/guide/en/observability/current/create-alerts.html Update Alerting Screenshots for Status Value Changes observability-docs#2455

• Security documentation: TBD. No obvious screenshots or text affected, but will double-check with @nastasha-solomon

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)