feat: Add Original PVC context to the deployment labels.

[farcaller]

Pull Request template

Why is this PR required? What issue does it fix?:

This allows targeting the nfs workload pod using stable labels in e.g. CiliumNetworkPolicy rules. Currently the only label on the workload is openebs.io/nfs-server with the generated pvc name which cannot be deduced statically from the original pvc name.

What this PR does?:

Adds the name/namespace/id labels to the pod.

Does this PR require any upgrade changes?:

No.

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

Using the pod in the CiliumNetworkPolicy, by targeting the new labels.

Any additional information for your reviewer? :

N/A

Checklist:

• Fixes #
• PR Title follows the convention of <type>(<scope>): <subject>
• Has the change log section been updated?
• Commit has unit tests
• Commit has integration tests
• (Optional) Does this PR change require updating NFS-Provisioner Chart? If yes, mention the Helm Chart PR #
• (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
• (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

[t3hmrman]

@abhilashshetty04
@niladrih
@pawanpraka1

Sorry to bother ya'll, -- this is a really useful feature, is it possible to merge & release it?

[abhilashshetty04]

@avishnu

[niladrih]

Thank you for the PR @farcaller. And thanks for the bump @t3hmrman. The CI checks seem to have not run, I'm putting the do-not-merge label on this one for a while.

[niladrih]

Not sure what went wrong with the CI here, manual runs seem to pass. Accepted!