Propagate annotations and labels from CRDs to secrets

[archi-team-cacd2]

Hello,

My use case requires to be able to manage annotations and labels on the Kubernetes secrets.
This enhancement proposes to propagate the labels and annotations of the CRDs to the secrets (it could be covered by a feature flag if this assumption is not applicable for all users).

As I'm not able to run the unit tests on my local environnement, it may not currently handle all cases.
However, it seems to be working fine on my Kubernetes cluster for a new secret.

Best regards

[akloss-cibo]

This change creates problems for managing vault CRDs with ArgoCD. ArgoCD injects a label into the vault CRD indicating that the object is managed by ArgoCD, then vault-crd copies that label into the secret, and ArgoCD thinks the secret is managed by itself and will remove the secret. Repeat. A flag to control this behavior or a filtering regex or something would be lovely.

[akloss-cibo]

I created #53 which creates an annotation to list the labels to copy, which solves my ArgoCD secret problem. I also created #52 and #51 which are nice-to-haves. I couldn't make ./mvnw test complete successfully on master, so I skipped creating tests.