Fix : Pods not being annotated with kubearmor-policy=enabled by Kubearmor controller

[Aryan-sharma11]

Purpose of PR?:

Fixes #CI failure for BPFLSM

Context -
We updated the dependencies for controller runtime to v0.15.3 in.
Apparently, after v0.15the injection pkg is removed, causing the decoder to be created with a nil value in our kubearmor controller code.

The change in this PR is made in accordance with the updated logs of kubernetes-sigs controller-runtime.

How we verified the error

• whenever a new deployment was created we tried to update the annotation of the pod through the (a *PodAnnotator) Handle() function this caused panic in the controller logs.

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

• Build KubarmorController locally , and try to deploy a new pod. Watch controller logs kubectl logs -n kubearmor<> -f.
  There should be no panic error in logs.
  Additional information for reviewer? :
  Mention if this PR is part of any design or a continuation of previous PRs

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