Add juju-doctor probe to validate COS deployments for telemetry correlation #112
Description
Our newest telemetry correlation feature has a number of (rather implicit) deployment topology requirements.
E.g. if Tempo is related to Loki, and loki is related to Grafana, but tempo is related to (a different Grafana), for some reason, things will be subtly broken.
So this probe should validate that there are no strange things going on with the deployment (multiple mimir applications for instance, or multiple tempos)...