Fix fluentdconfig and syslogngconfig deletion

[OverOrion]

This PR aims to fix two problems:

• deleting a fluentdconfig/syslogngconfig resource should also delete the child resources (solved by changing the ownerreferences)
• deleting a logging resource should not be possible until a fluentdconfig/syslogngconfig resource exists. we don't delete the fluentdconfig/syslogngconfig forcefully because those are created by the user, but we can protect against this by using a finalizer. we send an event to the logging object for the user to be able to see other than looking at the operator logs

Fixes #1667.

Signed-off-by: Szilard Parrag szilard.parrag@axoflow.com

[OverOrion]

I have reworked the PR according to pepov's notes and using kubebuilder's docs: https://book.kubebuilder.io/reference/using-finalizers.

I also added a secondary fix which occured when logging switched from fluentdConfig to inline spec.