Implement base action automation for a selected incoming event

[ezodude]

Overview

Implement the features enabled by setting the configuration provided by #828.

Investigate how this can work with the existing sources router. That is, actions added to source / resource / event combo based on actions automation config to easily trigger an action.

Acceptance Criteria

• Configured automation is executed when a related k8s resource event is triggered.
• Can run automations with templated commands.
• A notification is sent to the appropriate channel when an automated action occurs (ideally through the k8s event system and not only through Botkube, so that the event is logged in the k8s infrastructure)
• Add any necessary unit tests.
• Add any necessary e2e tests.

Phases

• Execute actions when events are coming from bound source
• Execute actions even when users don't want to see the action outcome on channel
• Add E2E tests

Later, if needed:

• Emit K8s event when a given command is executed - Update: Confirmed with @brampling that it is not needed

Reason

Part of #789