Issue Description:
End users need to access runtime information to debug a problem or just to put in place some alerting/monitoring.
Currently all processor runtime information are hidden inside OSD logs and they are not accessible to the users.
There is no Red Hat shared end user observability stack so the idea is to let user configure a CloudWatch Logs instance where similar information can be sent

Acceptance Criteria:

• User can configure a CloudWatch instance to get tracing informations
• A log entry is created for each signification step (processor filtering, processor transformation, action application)

Out of Scope:

• RHOC logs (will require a different ticket)

Additional Information:

• Observatorium: upstream initiative that covers logging, metrics and in the future tracing too
• Quarkus - Logging Cloudwatch: extension that can used/considered to publish CloudWatch Logs entries