[RAC][Security Solution][Detections] Integrate Rule Execution Log into Detection Engine

[banderror]

Parent ticket: #101013

Summary

Integrate the implementation developed in #106461 into the new incarnation of Detection Engine being migrated to rule_registry.

• Integrate with BaseSecurity rule type implemented in [RAC][Security Solution] Add base Security Rule Type #105096.
  • Pass in generic status writer. Executors call generic status writer to write warning and errors during execution.
  • Integration with BaseSecurity rule type should be straightforward. We already have a "decorator" that can wrap rule types and inject a logger instance (Link).
• Make sure to write status change events both from generic parts of the execution logic (e.g. top-level exception handling, gap detection) and from specific rule type executors (e.g. ML rules have specific error logging). Go through the old Detection Engine and double-check that all statuses ("going to run", "warning", "failed", "succeeded") are written in all cases.
• Make sure to write all execution metrics as well.

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[xcrzx]

Implemented in #107624