Pod Security Standard label is set as annotation instead of label

[netthier]

Describe the bug
When installing DirectPV 4.0.2 via the CLI (kubectl directpv install), a directpv namespace gets created.
If a pod security standard is enforced in the cluster, no containers will start as they lack dont conform to those standards.
To fix this, the namespace should be labelled with pod-security.kubernetes.io/enforce: privileged.
Someone seems to have already noticed that, as exactly that already exists as an annotation, which is however incorrect.
https://kubernetes.io/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/

To Reproduce
Install DirectPV via kubectl directpv install with a Pod Security Standard being enforced in the cluster.

Expected behavior
I expect the namespace to be labelled as described above

Screenshots and logs

The annotation here should be a label instead.

Deployment information (please complete the following information):

• DirectPV version: 4.0.2
• Kubernetes Version: 1.26.3
• OS info: N/A
• Kernel version: N/A

[balamurugana]

Please check the PR #747