Rename chart names for OCI consistency

Proposed chart name changes to make OCI artifact names conform:

Core:

• Kiali: Rename chart to kiali (maybe pending operator discussion here)
• Kyverno Reporter: Rename chart to kyverno-reporter
• Elastic/Kibana: Rename chart to elasticsearch-kibana
• Fluentbit: Rename chart to fluentbit
• Monitoring: Chart will be split up, new names grafana and prometheus?
• Twistlock: Rename chart to prisma-cloud

Addons:

• ArgoCD: Rename chart to argocd
• Anchore: Rename chart to anchore

---

Notes from spike regarding feasibility:

Some charts use the .Chart.Name value for pod names, labels, etc. Our options will generally be:

1. Change the chart name, nothing uses it so there is no harm.
2. Change the chart name, upgrade works smoothly even with things using it.
3. Change the chart name, maintain old name for labels, etc via nameOverride value.
4. Leave the chart name as is because we will break too many things.
5. Change the chart name and leave chaos in our wake.

Core:

• Kiali: Provides nameOverride value
• Kyverno Reporter: Provides global.fullnameOverride value
• Elastic/Kibana: We built the chart and could add a nameOverride if we want, although we probably should just go all in on this one since we will be changing a lot of other things around it too
• Fluentbit: Provides nameOverride value
• Monitoring: Similar to logging, enough changes to other things surrounding this chart that we can probably rename it no problem
• Twistlock: Again same thing, we want to rename it fully

Addons:

• ArgoCD: Provides nameOverride value
• Anchore: Provides nameOverride value