Configure an OTEL collector on i03's beamline cluster

To use diamond's central tracing service, which is still in development, each beamline cluster will need to have an Open Telemetry collector service deployed. Using the helm chart in https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector is probably the easiest way to do this. We should consider adding it to ArgoCD as well.

Hyperion's collector will need to be able to see data from outside the cluster, since Hyperion isn't yet running on kubernetes. This will mean setting up an extra ingress. The linked helm chart's `values.yaml` seems like it provides an option for this.

See https://confluence.diamond.ac.uk/display/CLOUD/Design+-+Observability+Tools#DesignObservabilityTools-Tracing for more information

## Acceptance Criteria
- Collector service deployed on i03's kubernetes cluster with an ingress to see Hyperion
- Hyperion writes data to the collector
- Collector configured to forward data to the central collector service