Avoid overwrtiging existing apparmor profiles

[ccojocar]

What type of PR is this?

/kind bug

What this PR does / why we need it:

This adds a measure in place to avoid overwriting existing apparmor profiles when a new profile
is first installed by checking the Generation field of the CRD. In this way, it always to
update existing profiles which were already installed by the security-profiles operator.

This is a measure to prevent that an attacker will overwrite an existing profile which is already
loaded into the node to alter its permissions.

Which issue(s) this PR fixes:

Does this PR have test?

yes

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Add a measure in place to avoid overwriting existing apparmor profile when a profile is first 
intalled.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ccojocar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ccojocar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ccojocar]

/retest

[k8s-ci-robot]

@ccojocar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-security-profiles-operator-verify	872cc54	link	true	/test pull-security-profiles-operator-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.