Internal eventing and reconciliation logic are missing key trace info for troubleshooting purpose

[davoustp]

When attempting to understand why the operator was constantly under pressure (see #103, now fixed by recent commit 0cab7b3 ), enabling debug log level was not enough to understand what was happening under the hood.

More specifically, debug logs were missing for:

• incoming Kubernetes events triggering reconciliation
• operations performed against Vault
• drift detection outcome

It is therefore pretty difficult to understand where the problems were coming from.

These key info need to be included at debug level to ease investigation.