Connector action retries in the event-log

[kobelb]

Feature Description

When a connector action fails and is being retried, log entries are not written to the .kibana-event-log-* indices and they do not show up in the Connector Logs UI. This creates a very confusing experience for our users because these failures are logged in the Kibana server logs, and the connector action success rate metrics exposed via /api/task_manager/metrics reflect these task failures.

When connector actions are ran, they should be included in the event-log, even if they are a retry. Additionally, it should be obvious via the Connector logs UI when a connector action is being ran as a result of the retry, how many retries are remaining, and when an attempt is the final attempt.

Business Value

Visibility into when connector actions are being retried.

Definition of Done

• All connector action attempts are written to the event-log
• The event-log denotes that the connector action was attempted to be ran as part of a retry
• The final failure of the connector action attempt should be explicitly denoted
• Unit tests

[elasticmachine]

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