Upgrade Grafana Operator to v5 on all clusters

[wmhutchison]

Describe the issue Manual investigation of this Operator revealed that while the current installation still functions (v4), it is no longer a version maintained actively and thus should be migrated to the newer and supported v5 branch. This ticket will track effort spent towards the research and development of this upgrade in a LAB cluster, and implement as needed on all PROD clusters. Additional documentation will be created in the form of new tickets using the ZenHub OCP upgrade ticket generator so that this operator will not be forgotten in future upgrades.

Additional context Github page for Grafana Operator

How does this benefit the users of our platform? This benefits internal users (Platform Services and Platform Operations) by having software which is directly still maintained with bugfixes and new features.

Definition of done

• [ ] Upgrade Grafana in a LAB cluster and work out all of the issues.
• [ ] Test the upgrade in remaining LAB clusters.
• [ ] Submit suitable CCM PR to promote into PROD clusters.
• [ ] Submit PR for adding a ticket to track this operator in future Openshift upgrades.

[wmhutchison]

Operator repo provides the following link for migrating from v4 to v5. Will inspect our manifests to see if we'll need to modify our Custom Resource content or not. https://grafana.github.io/grafana-operator/blog/2023/05/27/v4-to-v5-migration/