chore(deps): update helmrelease to helm.toolkit.fluxcd.io/v2

[renovate]

This PR contains the following updates:

Package	Update	Change
HelmRelease	patch	helm.toolkit.fluxcd.io/v2beta2 -> helm.toolkit.fluxcd.io/v2

---

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.

Based on the "git diff" provided, the changes made in the .yaml files relate to the update of the API version from v2beta2 to v2 for various HelmReleases across different Kubernetes applications and addons. From a security standpoint, assuming the newer API version (v2) is stable and has no known vulnerabilities, there do not appear to be direct security issues introduced by these changes.

However, there are a few considerations that are not strictly security vulnerabilities but are best practices in ensuring the security and stability of your deployment:

1. Deprecation Concerns: Ensure that v2 of the API does not deprecate any features you rely on without providing an alternative. Feature deprecation can lead to unexpected behavior that might indirectly affect the security posture of your deployment.

2. Compatibility Check: Before making such updates, it's crucial to verify that all your applications and their dependencies are fully compatible with the new API version (v2). Incompatibility could lead to service disruption and indirectly affect security by potentially disabling security features or fail-safes.

3. Change Log Review: This is not a direct security measure from the diff provided but a general recommendation. It's beneficial to review the change log or release notes for the new API version (v2) for any notable changes, improvements, or fixes related to security. This can include security patches, enhanced security features, or changes in default configurations that improve security.

4. Testing: Before rolling out these changes to a production environment, thorough testing (including security regression testing) is recommended. This ensures that the update doesn't introduce vulnerabilities or affect the application's security posture.

5. Configuration Check: The update does not show changes in configurations that might be supported or required by the new API version. Ensure that your HelmRelease configurations align with best practices for security for v2 of the API.

Based on the provided diff, without additional context on the specific differences in API behavior or features between v2beta2 and v2, and without visibility into the rest of your environment and configurations, there were no security issues that could be identified directly from these changes.

Suggested Markdown for Fixes or Checks

Given the analysis, direct security-related fixes might not be applicable, but here are suggestions for checks or actions in markdown format:

## Security Checks for API Version Upgrade from `v2beta2` to `v2`

Before applying these changes in a live environment:

1. **Compatibility Check**: Ensure all applications and dependencies are compatible with API version `v2`.

2. **Review Change Log**: Examine the change log or release notes for version `v2` with an eye on security updates or breaking changes.

3. **Test Thoroughly**: Conduct comprehensive testing including:
   - Functional testing
   - Security regression testing
   - Performance benchmarking

4. **Configuration Review**: Audit and adjust HelmRelease configurations to adhere to the security best practices recommended for the new API version.

5. **Continuous Monitoring**: After deployment, continuously monitor the applications and infrastructure for any anomalous behavior or issues.

Without specific security vulnerabilities introduced by the change in API version, these general best practices and preventive measures are recommended actions.