Fix label treatment of related charms

[sed-i]

Issue

Telemetry reaches prom/loki with incorrect labels.

Solution

• Render instance name from fqdn instead of topology identifier.
• Add cos-tool, similar to Fix label treatment of related charms grafana-agent-k8s-operator#277.

Fixes #60.

Drive-by fixes:

• Fetch-lib
• Add .wokeignore to .jujuignore
• Update issue templates

Context

Testing Instructions

Deploy something like this bundle:

series: jammy
saas:
  loki:
    url: microk8s:admin/pebnote.loki
  loki2:
    url: microk8s:admin/pebnote.loki2
  prom:
    url: microk8s:admin/pebnote.prom
applications:
  cp:
    charm: local:cos-proxy-1
    num_units: 1
  ga:
    charm: local:grafana-agent-3
  nrpe:
    charm: nrpe
    channel: edge
    revision: 117
  ub:
    charm: ubuntu
    channel: edge
    revision: 24
    num_units: 1
  ub2:
    charm: ubuntu
    channel: edge
    revision: 24
    num_units: 1
  zk:
    charm: zookeeper
    channel: 3/edge
    revision: 126
    num_units: 1
relations:
- - ga:juju-info
  - ub:juju-info
- - ga:logging-consumer
  - loki:logging
- - ga:send-remote-write
  - prom:receive-remote-write
- - cp:monitors
  - nrpe:monitors
- - nrpe:general-info
  - ub2:juju-info
- - cp:downstream-logging
  - loki2:logging
- - cp:downstream-prometheus-scrape
  - prom:metrics-endpoint
- - zk:cos-agent
  - ga:cos-agent

When related to prometheus, you should see an instance label for the grafana-agent hostname:

$ curl -s 10.1.166.117:9090/api/v1/label/instance/values | jq  # PROMETHEUS
{
  "status": "success",
  "data": [
    "10.238.171.191:5666",
    "juju_799803_2_lxd",
    "pebnote_897e972f-2c41-42e3-88bd-c1298f707c61_prom_prom/0"
  ]
}

$ curl -s 10.1.166.109:3100/loki/api/v1/label/instance/values | jq  # LOKI
{
  "status": "success",
  "data": [
    "juju_799803_2_lxd"
  ]
}