fix(argo-cd): Preserve component suffixes for long release names

[ystkfujii]

Summary

This PR fixes resource name rendering for the argo-cd chart when using long Helm release names.

Previously, some resources appended suffixes such as -metrics, -grpc, or -health-configmap after rendering the component fullname. With long release names, this could either exceed Kubernetes name length limits or truncate away the component-specific suffix, which could lead to invalid or colliding resource names.

This change adds a component-aware fullname helper that reserves space for the component suffix before truncating the base release name. It also updates metrics Services, Redis health ConfigMap references, and Argo CD server gRPC resource names to use dedicated helpers.

Closes #3840.

Upgrade impact

For normal release names, rendered resource names should remain unchanged.

For very long release names, some existing resources may be renamed because suffixes such as repo-server, redis, metrics, grpc, and health-configmap are now preserved.

Notes

Ideally, the helper could include a deterministic hash of the full base name to distinguish releases that share the same long prefix. This PR does not add such a hash and only preserves component suffixes while truncating the base name. If a follow-up issue is raised for collisions between multiple long release names with the same prefix, I am happy to address that separately.

I considered adding a regression test for this boundary case. If maintainers think it is necessary, I can add a small shell script that renders the chart with a 53-character release name and verifies that rendered resource names stay within the Kubernetes name length limit and do not collide, then run it as a dedicated GitHub Actions step.

Checklist:

• I have bumped the chart version according to versioning
• I have updated the documentation according to documentation
• I have updated the chart changelog with all the changes that come with this pull request according to changelog.
• Any new values are backwards compatible and/or have sensible default.
• I have signed off all my commits as required by DCO.
• I have created a separate pull request for each chart according to pull requests
• My build is green (troubleshooting builds).