Add alert and action plugin console logging (ease of debugging)

[mikecote]

We should do an audit of the debug logs we do for alerts and actions plugin. We should add logs in missing areas that would facilitate debugging issues on a remote install.

Some examples of visibility that logging should be providing (note some may already be done):

• When did my alert run last?
• Did my alert have any active instances when it ran?
• What actions got fired from my alert execution?
• Did any alert action get throttled?
• Errors that happened during alert or action execution

NOTE:
This issue is in the same area as #62337 and could be worked on at the same time.

Original description

We currently don't have any console logging within the alerting plugins. We should add some debug logs to facilitate debugging issues on a remote install.

[elasticmachine]

Pinging @elastic/kibana-stack-services (Team:Stack Services)

[mikecote]

It's also hard to debug the output search query an alert uses. A debug log would be useful in some alert types.