feat(operator): allow to set log level

[carlosrodfern]

Fixes: #1566

Purpose of PR?:

To allow the operator and the snitch to receive a log level flag from the command line arguments.

Fixes #1566

Does this PR introduce a breaking change? No

If the changes in this PR are manually verified, list down the scenarios covered:: deployed the operator and tested that info and error level do work as expected.

Additional information for reviewer? :

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

[carlosrodfern]

The cmd argument naming conventions I see used in the operator and snitch are "alllowecase" and "camelCase", but since the camelCase is used the most I went with loglevel. However, the controller uses the "kebab-case" for logs since it just lets the SIG zap (not the uber zap used in the operator and snitch) parse it, e.g., --zap-log-level.

On a different note, once this is merged and the new operator released, the corresponding helm chart will need updates to allow set those log level values in the values.yaml. I'll provide a PR for that one as well.

[carlosrodfern]

The ci is failing because kube is failed to apply the kubearmor-policy in the test to an existing pod. It doesn't appear to be related with this PR change.

[DelusionalOptimist]

LGTM.