[module-manager] helm can't detect configuration drift on startup

[miklezzzz]

Expected behavior (what you expected to happen):

Actual behavior (what actually happened):
When modulerun is called, the operator compares two checksums, one - for all manifests of the module produced by helm render, another - for all manifests stored in the current helm release of the module in the cluster. If checksums are different, helm upgrade is performed. This way, it can't detect if any changes to the module's resource in the cluster were applied manually (kubectl edit).

Steps to reproduce:
create a module
update the module's resource (deployment, etc) in the cluster with kubectl edit
restart operator and check if the resource configuration was reverted to the previous config

Environment:

• Addon-operator version:
• Helm version:
• Kubernetes version:
• Installation type (kubectl apply, helm chart, etc.):

Anything else we should know?:

Additional information for debugging (if necessary):

Hook script

Logs