chore(deps): update helmrepository to source.toolkit.fluxcd.io/v1

[renovate]

This PR contains the following updates:

Package	Update	Change
HelmRepository	patch	source.toolkit.fluxcd.io/v1beta2 -> source.toolkit.fluxcd.io/v1

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

No security issues could be directly identified from the given "git diff" that specifically modifies the version of APIs from v1beta2 to v1 for various Helm repositories in Kubernetes templates and configurations.

Evaluation Context:

• The changes are related to the update of apiVersion from a beta version (v1beta2) to a stable version (v1), across multiple Helm repository configurations.
• Transitioning from beta to stable API versions typically implies that the APIs have become stable and feature-complete, reflecting a maturity that could include security improvements and removal of deprecated features.

Considerations:

1. API Version Compatibility: Ensure that the target Kubernetes cluster where these Helm repositories are being deployed supports the v1 API version for these resources. This is usually the case with newer Kubernetes versions, but compatibility must be verified to avoid deployment issues.

2. Helm Chart Compatibility: Some Helm charts may have specific requirements or dependencies based on the apiVersion. It’s crucial to ensure that all referenced Helm charts in these configurations are compatible with the newer v1 API version to prevent runtime errors or misconfigurations.

3. Template and Configuration Updates: Though not directly a security concern, it’s advisable to review the templates and configurations for any other changes necessitated by the API version update. This includes verifying property names, required fields, and default values that might have changed between v1beta2 and v1.

Suggested Action:

• Review and Test: Before applying these changes to a production environment, thoroughly review and test the updated configurations in a development or staging environment. This testing should confirm both functional performance and security posture to ensure no new vulnerabilities are introduced.

• Documentation and Change Log: Maintain detailed documentation of these changes, including the reason for updating API versions (e.g., deprecation of v1beta2, stability improvement, additional features in v1) and any modifications made to Helm charts or Kubernetes configurations as a result.

Given the provided "git diff", there were no direct security issues identified. However, the considerations and actions suggested above are critical for maintaining security and operational integrity during and after such updates.