Anchor metrics

[Zacholme7]

Setup anchor with Prometheus

[oleg-ssvlabs]

I think with this approach, we’ll lose the metrics from the github.com/ethpandaops/ethereum-package package (network-related metrics).
It would be better if we could aim to retain those network-related metrics and also provide the ability to configure the existing Prometheus instance to scrape additional targets.
SSV Nodes also expose a lot of metrics, and we have various dashboards relying on them, so we definitely want Prometheus to scrape the SSV Nodes as well.

Essentially, we have two approaches.

• Configure Prometheus manually and remove its config from the ethereum-package stack. Manually configured(what this PR does basically) should be configured to scrape Anchor/SSV nodes and also the blockchain network itself (CL/EL nodes, etc).
• Run Prometheus as part of the ethereum-package stack (how it works today) and verify there is an ability to fetch kurtosis Prometheus service and add the configuration to scrape more targets (SSV/Anchor nodes).

Personally, I like the first approach. It is more manual and will provide more flexibility. However, we just need to verify it's achievable. So the goal is: we want to have Prometheus and Grafana up and running and we want to have full flexibility of removing/adding/updating Prom and Grafana configurations.

Wdyt?