add custom labels and annotations for crds

[UndeadDemidov]

Add custom labels and annotations support for CRDs

Summary

This PR adds the ability to configure custom labels and annotations for CloudNativePG CRDs through Helm values. This enhancement is particularly useful for ArgoCD users who need to enable server-side apply for CRDs managed by ArgoCD.

Changes

• Added crds.labels and crds.annotations configuration options in values.yaml
• Updated values.schema.json to include validation for the new fields
• Modified CRD templates to apply custom labels and annotations to all CRDs:
  • backups.postgresql.cnpg.io
  • clusterimagecatalogs.postgresql.cnpg.io
  • clusters.postgresql.cnpg.io
  • databases.postgresql.cnpg.io
  • failoverquorums.postgresql.cnpg.io
  • imagecatalogs.postgresql.cnpg.io
  • poolers.postgresql.cnpg.io

Use Case

This feature enables ArgoCD users to add annotations like argocd.argoproj.io/sync-options: ServerSideApply=true to CRDs, which is required for proper CRD management in ArgoCD environments.

Example Usage

crds:
create: true
labels:
app.kubernetes.io/managed-by: argocd
annotations:
argocd.argoproj.io/sync-options: ServerSideApply=true

Tests

This commit locally tested in k3d+argocd

[itay-grudev]

I can accept this if you modify the RELEASE.md to include a command(s) that automatically adds the new yaml. Otherwise, with the current release procedure, the moment we do another release, your changes will be lost.