Migrate from `helm/v1-alpha` (deprecated) to `helm/v2-alpha`

## :dart: What is the goal?
Stop using the deprecated [helm/v1-alpha](https://book.kubebuilder.io/plugins/available/helm-v1-alpha.html) plugin and migrate this repository to [helm/v2-alpha](https://book.kubebuilder.io/plugins/available/helm-v2-alpha.html).

## 🚀 Why adopt [helm/v2-alpha](https://book.kubebuilder.io/plugins/available/helm-v2-alpha.html)?
- [helm/v1-alpha](https://book.kubebuilder.io/plugins/available/helm-v1-alpha.html) was an initial experimental version created to collect community feedback, and **it is now deprecated**.

- [helm/v2-alpha](https://book.kubebuilder.io/plugins/available/helm-v2-alpha.html) includes bug fixes, improvements, follows common Helm best practices, and adds enhancements from that feedback. It provides a more flexible chart workflow: it generates charts from kustomize output, preserves common customizations, and supports extra options (for example, changing the default chart output path). Also, `values` is now more complete and exposes better configuration options for your consumers.

## :hammer_and_wrench: What are the steps to start using [helm/v2-alpha](https://book.kubebuilder.io/plugins/available/helm-v2-alpha.html)?
1. Copy the current Helm chart into a backup directory (keep it for reference).
2. Make sure you are using the latest local Kubebuilder release: https://github.com/kubernetes-sigs/kubebuilder/releases
3. Delete the current chart directory.
4. Re-generate the Helm scaffolding with: kubebuilder edit --plugins=helm/v2-alpha
5. Compare the new chart with the backup and re-apply any repo-specific changes (if any), like `Chart.yaml` updates or other customizations.

**Note**: _Created automatically after detecting `helm/v1-alpha` in the PROJECT file._

Inspecciona el archivo PROJECT y el chart actual de Helm, y luego crea una copia de seguridad tal como se describe. Usa la versión local más reciente de Kubebuilder para ejecutar `kubebuilder edit --plugins=helm/v2-alpha`, compara el chart regenerado con la copia de seguridad y vuelve a aplicar las personalizaciones específicas del repositorio, como las actualizaciones de Chart.yaml.

Escrito por el modelo de indexación a partir del texto del issue.