[CWS] Report rule actions in events

[lebauce]

What does this PR do?

Report the actions associated to the triggered rule in the event sent to the backend.

Motivation

Actions are not part of the sent event which makes it necessary to correlate with
remote config to match event with the rule actions.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.

[alai97]

No docs review needed.

[paulcacheux]

I'm not a fan of map[string]interface{}, why not using a real struct type ? This would simplify the SendEvent later down

[Gui774ume]

LGTM !
I think we can simply use a string instead of an interface, unless you have something in mind. But overall it doesn't change anything for the backend and more specifically the kill action, so we can always revisit later if need be.