[alerts] add executionStatus to event log doc for action execute (#82401

)

resolves #79785

Until now, the execution status was available in the the event
log document for the execute action.  In this PR we add it.

The event log is extended to add the following fields:

- `kibana.alerting.status` - from executionStatus.status
- `event.reason`           - from executionStatus.error.reason

The date from the executionStatus and start date in the event
log will be set to the same value.

Previously, errors encountered while trying to execute an
alert executor, eg decrypting the alert, would not end up
with an event doc generated.  Now they will.

In addition, there were a few places where events that could
have had the action group in them did not, and one where the
instance id was undefined - those were fixed up.

x-pack/plugins/alerts/server/alert_instance/alert_instance.ts

@@ -51,6 +51,10 @@ export class AlertInstance<
  return false;
  }
 
+ getLastScheduledActions() {
+ return this.meta.lastScheduledActions;
+ }
+
  getScheduledActionOptions() {
  return this.scheduledExecutionOptions;
  }

x-pack/plugins/alerts/server/task_runner/create_execution_handler.test.ts

@@ -113,6 +113,7 @@ test('enqueues execution per selected action', async () => {
  },
  "kibana": Object {
  "alerting": Object {
+ "action_group_id": "default",
  "instance_id": "2",
  },
  "saved_objects": Array [

x-pack/plugins/alerts/server/task_runner/create_execution_handler.ts

@@ -116,6 +116,7 @@ export function createExecutionHandler({
  kibana: {
  alerting: {
  instance_id: alertInstanceId,
+ action_group_id: actionGroup,
  },
  saved_objects: [
  { rel: SAVED_OBJECT_REL_PRIMARY, type: 'alert', id: alertId, ...namespace },