fix(enforcer/bpflsm): panic during bpflsm cleanup

[daemon1024]

Purpose of PR?:

• panic during bpflsm cleanup
• fix missing proc name in alerts

Does this PR introduce a breaking change?

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

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

[Aryan-sharma11]

The changes makes sense, although I noticed one thing, if in case BPFLSM fails to load we move on to AppArmor, so if we install Kubearmor using operator ,it would still be showing podname kubermor-bpf-crio even if we are running apparmor under the hood.
Can we handle that wdyt?

[daemon1024]

@Aryan-sharma11 I don't think we can handle that right now. But we need to think about how to handle that in the operator refactor. Let's handle that seprately.