Prometheus integration

[sharonsyh]

This pull request introduces Prometheus-based metric tracking for energy and power usage within the Zeus framework. It includes functionality for monitoring GPU, CPU, and DRAM energy usage via Histograms, Cumulative Counters, and Gauges.

• zeus/metric.py:
  A new module that introduces EnergyHistogram, EnergyCumulativeCounter, and PowerGauge classes. These classes enable real-time monitoring of CPU, GPU, and DRAM energy and power consumption by integrating with Prometheus.

• zeus/prometheus.yml:
  Configuration file for setting up Prometheus monitoring.

• zeus/docker-compose.yml:
  A Docker Compose file for easily setting up Prometheus with the project for local or cloud-based monitoring.

• Modified pyproject.toml:
  Added prometheus-client as an optional dependency for Prometheus metric integration.

[jaywonchung]

Some quick points:

• The two YAML files do not belong in zeus/. Please move them into docker/. If appropriate, feel free to create a subdirectory inside docker/.
• Merge conflicts should be resolved and CI should pass.
• Tests and documentation (under docs/) are missing. If you're not sure about how to write the doc, let's discuss separately.

[jaywonchung]

For all files, please make sure they end with a newline. It's an editor issue.

[jaywonchung]

Why was push_docker.yaml modified in the first place? I see that this branch has old commits from when you added the multi-arch docker image feature, suggesting that you continued working on an old merged branch instead of creating a new branch for Prometheus integration. If push_docker.yaml was modified in master separately, this will create a merge conflict. Instead of trying to resolve this merge conflict, I would rather create a fresh new branch from master and just copy over the new/modified files to the new branch. If you decide to do that, we can just close the PR and you can open a new PR with the new branch.

#106 (review)
This is the second time you reused an old branch and I already asked you not to.

[sharonsyh]

Why was push_docker.yaml modified in the first place? I see that this branch has old commits from when you added the multi-arch docker image feature, suggesting that you continued working on an old merged branch instead of creating a new branch for Prometheus integration. If push_docker.yaml was modified in master separately, this will create a merge conflict. Instead of trying to resolve this merge conflict, I would rather create a fresh new branch from master and just copy over the new/modified files to the new branch. If you decide to do that, we can just close the PR and you can open a new PR with the new branch.

#106 (review) This is the second time you reused an old branch and I already asked you not to.

I realized my newly created prometheus-integration branch was created from a branch that had already been merged. I will create a fresh branch from master, copy the new or modified files over, and open a new PR.