feat: [sc-10649] Expose Metrics in Ghost

[teghnet]

Trying to expose new service through TOR, but we need to discuss more.

• https://discord.com/channels/850545426251251732/1340016828226998446
• https://github.com/chronicleprotocol/suite/pull/363

[teghnet]

pending some discussions
cc: @MDobak

[WesleyCharlesBlake]

the tor-proxy chart is not used any more since we handle the deployment of tor/onion resources using the CRD's. please remove the tor-proxy changes from the pr.

Then to get ghost metrics port, we can update this

    - port:
        number: 8888
      backend:
        service:
          name: ghost
          port:
            number: {{ .Values.ghost.service.ports.webapi.port }}
    - port:
        number: 9999
      backend:
        service:
          name: {{ include "validator.fullname" . }}-metrics
          port:
            number: 9090

[WesleyCharlesBlake]

oh and we would need to update the metrics service

[teghnet]

1. We are not exposing 9999 on TOR (yet?)
2. We separate metrics from healthchecks.
3. Healthchecks = livez + readyz
4. Port 9100 is for healthchecks, meaning: both liveness and readyness

[teghnet]

because healthz is deprecated

[teghnet]

It is very unlikely that we would expose webapi here.
As an example, it's OK, but the metrics below are configured elswhere and keeping them here would confuse folks.