Purpose of PR?:

Introduces a new field karmor.yaml in the ConfigMap kubearmor-config created by KubeArmor Operator. This field can be mounted into KubeArmor Pods so that the configuration can be done by Viper, deprecating Config Watcher in KubeArmor

Fixes #1920

Does this PR introduce a breaking change?

Configuration using karmor.yaml will eventually replace the other fields in the config map

If the changes in this PR are manually verified, list down the scenarios covered::
Verified both fields in config map are having same values

Additional information for reviewer? :
Continuation of #1862

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests