refactor: use ${releaseName}-${appVersion} prefix in resources

[takirala]

What problem does this PR solve?:

I bumped the version of apps only if they haven't been bumped since 2.16.0
No functional changes were made to underlying applications.

Which issue(s) does this PR fix?:

Special notes for your reviewer:

Summary

This PR contains two major refactoring efforts:

1. OCIRepository naming standardization - Standardized all OCIRepository resource names to use template variables
2. Version path bumping - Prepared 12 applications for patch version updates

---

1. OCIRepository Naming Standardization

Standardized OCIRepository and ConfigMap resource names and corresponding HelmRelease chartRef.name and values references to use template variables (${releaseName}-${appVersion}-*) instead of hardcoded names.

Applications Refactored (11 total)

Single OCIRepository Applications

• ai-navigator-cluster-info-agent (2 OCIRepositories)
  • Main: ${releaseName}-${appVersion}-chart
  • API: ${releaseName}-${appVersion}-api

Multi-OCIRepository Applications

1. harbor (5 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • Components: valkey, database, manual-storage, cosi-bucket-kit

2. cert-manager (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • CRDs: ${releaseName}-${appVersion}-crds

3. cosi-driver-nutanix (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • COSI: ${releaseName}-${appVersion}-cosi-bucket-kit

4. gatekeeper (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • Proxy: ${releaseName}-${appVersion}-proxy-mutations

5. knative (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • Operator: ${releaseName}-${appVersion}-operator

6. logging-operator (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • Logging: ${releaseName}-${appVersion}-logging

7. project-grafana-loki (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • OBC: ${releaseName}-${appVersion}-object-bucket-claim

8. traefik (2 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • CRDs: ${releaseName}-${appVersion}-crds

9. rook-ceph-cluster (3 OCIRepositories)

   • Main: ${releaseName}-${appVersion}-chart
   • OBC: ${releaseName}-${appVersion}-object-bucket-claim
   • COSI: ${releaseName}-${appVersion}-cosi-bucket-kit

10. istio-helm (5 OCIRepositories)

    • Components: base, cni, istiod, ztunnel, gateway

Naming Pattern

• Single OCIRepository apps: Use ${releaseName}-${appVersion}-chart
• Multi-OCIRepository apps: Use descriptive suffixes (e.g., -crds, -api, -operator, -logging)

---

2. Version Path Bumping

Bumped patch versions for 12 applications by updating path references and renaming version directories. Chart tags remain unchanged as these versions don't exist upstream yet.

Applications Updated

Application	Old Version	New Version
ai-navigator-app	0.5.1	0.5.2
ai-navigator-cluster-info-agent	0.4.1	0.4.2
ai-navigator-rag	0.7.3	0.7.4
grafana-loki	0.80.4	0.80.5
istio	1.23.4	1.23.5
jaeger	2.57.2	2.57.3
kubefed	0.11.2	0.11.3
kubernetes-dashboard	7.13.0	7.13.1
rook-ceph	1.17.6	1.17.7
rook-ceph-cluster	1.17.6	1.17.7
thanos	15.8.1	15.8.2
vgpu-token-operator	1.0.7	1.0.8

Changes Made

• ✅ Updated all path: references in helmrelease.yaml, kustomization.yaml, and related files
• ✅ Renamed version directories using git mv to preserve history (106 files moved)
• ✅ Updated dependency references (e.g., prereq job names for rook-ceph-cluster)
• ❌ Chart tags remain unchanged - All OCIRepository chart tags stay at current versions

---

Impact

• 11 applications standardized for OCIRepository naming consistency
• 12 applications were bumped
• Better alignment with catalog v2 layout

Testing

• Verified all path references point to correct new version directories
• Confirmed chart tags remain unchanged
• Validated directory renames preserve git history
• Verified OCIRepository naming follows consistent pattern

[takirala]

Will follow up if there are more changes. This is not tested end to end yet.