fix(docs): update values.yaml path for prometheus (#757)

# Description

1. fix broken path for Prometheus values.yaml path (Helm deployment)
2. clean-up the bullet points numbering

## Related Issue

If this pull request is related to any issue, please mention it here.
Additionally, make sure that the issue is assigned to you before
submitting this pull request.

## Checklist

- [x] I have read the [contributing
documentation](https://retina.sh/docs/contributing).
- [x] I signed and signed-off the commits (`git commit -S -s ...`). See
[this
documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification)
on signing commits.
- [x] I have correctly attributed the author(s) of the code.
- [x] I have tested the changes locally.
- [x] I have followed the project's style guidelines.
- [x] I have updated the documentation, if necessary.
- [x] I have added tests, if applicable.

## Screenshots (if applicable) or Testing Completed

Please add any relevant screenshots or GIFs to showcase the changes
made.

## Additional Notes

Add any additional notes or context about the pull request here.

---

Please refer to the [CONTRIBUTING.md](../CONTRIBUTING.md) file for more
information on how to contribute to this project.

Signed-off-by: Simone Rodigari <[email protected]>

Author: SRodi

docs/02-Installation/04-Grafana/prometheus-unmanaged.md

@@ -15,44 +15,42 @@
   helm repo update
   ```
 
-2. Save **[these Prometheus values](https://github.com/microsoft/retina/blob/main/deploy/legacy/prometheus/values.yaml)** below to `deploy/legacy/prometheus/values.yaml`
-
-3. Install the Prometheus chart
+2. Install the Prometheus chart
 
   ```shell
-  helm install prometheus -n kube-system -f deploy/prometheus/values.yaml prometheus-community/kube-prometheus-stack
+  helm install prometheus -n kube-system -f deploy/legacy/prometheus/values.yaml prometheus-community/kube-prometheus-stack
   ```
 
 Or if you already have the chart installed, upgrade how you see fit, providing the new job name as an additional scrape config, ex:
 
   ```shell
-  helm upgrade prometheus -n kube-system -f deploy/prometheus/values.yaml prometheus-community/kube-prometheus-stack
+  helm upgrade prometheus -n kube-system -f deploy/legacy/prometheus/values.yaml prometheus-community/kube-prometheus-stack
   ```
 
 Note: Grafana and kube-state metrics may schedule on Windows nodes, the current chart doesn't have node affinity for those components. Some manual intervention may be required.
 
-6. Verify that the Retina Pods are being scraped by port-forwarding the Prometheus server:
+3. Verify that the Retina Pods are being scraped by port-forwarding the Prometheus server:
 
   ```shell
   kubectl port-forward --namespace kube-system svc/prometheus-operated 9090
   ```
 
-7. Then go to [http://localhost:9090/targets](http://localhost:9090/targets) to see the Retina Pods being discovered and scraped:
+4. Then go to [http://localhost:9090/targets](http://localhost:9090/targets) to see the Retina Pods being discovered and scraped:
 
 ![alt text](../img/prometheus-retina-pods.png)
 
 ## Configuring Grafana
 
 Create a Grafana instance at [grafana.com](https://www.grafana.com) and follow [Configuring Grafana](./grafana.md), or use the one installed from above.
 
-8. Get the Grafana password:
+1. Get the Grafana password:
 
 ```shell
 kubectl get secret -n kube-system prometheus-grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo
 ```
 
-9. Import the new dashboard from **[here](https://grafana.com/grafana/dashboards/18814/)**.
+2. Import the new dashboard from **[here](https://grafana.com/grafana/dashboards/18814/)**.
 
-10. Metrics should be visible:
+3. Metrics should be visible:
 
 ![alt text](../img/grafana-dashboard-metrics.png)