🚀 Add podLabels value to add custom labels to operator pods

[mlflr]

Description

This PR adds podLabels value that is added to pod labels of operator deployment as is customary in most helm charts.
In many organizations it is mandatory to have specific labels in order to facilitate for, for example, cost allocation or log ingestion

Usage Example

adding this to values file:

podLabels:
  test: xxx
  test2: yyy

results in deployment having:

apiVersion: apps/v1
kind: Deployment
...
spec:
  ...
  template:
    metadata:
      labels:
        ...
        test: xxx
        test2: yyy
...

References

N/A

Community Note

• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

[hashicorp-cla-app]

All committers have signed the CLA.

[arybolovlev]

Hi @mlflr!

Thank you for your interest in contributing to this project!

Could you please do the following steps to complete it?

• Update Helm chart documentation. Please, execute make helm-docs.
• Add a change log entry:

  $ changie new --kind ENHANCEMENTS --custom "PR=522" --body '`Helm Chart`: Add the ability to configure additional labels for the Operator pod.'

[mlflr]

done

[arybolovlev]

Thank you, @mlflr! 🚀