Setup Prometheus Scraper Locally to Scrape API-Dev, Worker-Dev and Prometheus Metrics & Add Prometheus Scrapers as Data Source in Local Grafana

[vimscientist69]

Reason

Scraping api-dev and worker-dev metrics locally are important for understanding application behavior, debugging and monitoring locally with Grafana local instance.

Tech Details List

1. Setup prometheus service configuration in docker-compose.yml and configure prometheus scrapers with prometheus.yml
2. Add prometheus as a data source in grafana configuration
3. Reconfigure networks to not use network_mode: host, but instead use network groups (have a "monitoring" and "backend" group)

Tasks:

1. Setup prometheus service configuration in docker-compose.yml and configure prometheus scrapers with prometheus.yml
2. Add prometheus as a data source in grafana configuration
3. Reconfigure networks to not use network_mode: host, but instead use network groups (have a "monitoring" and "backend" group)
4. Improve startup time for api-dev and worker-dev docker-compose services by using persistent volumes to cache the .build directory

Un-important tasks:

• Update environment variable files in Obsidian so that when pull request is merged, @AdonisCodes can update their environment variables in Backend to not cause any issues
• Update environment variables in Github actions for testing (if needed) and secrets for sandbox fly.io app

Links:

ISSUE-78
closes/resolves #78

Testing

Steps:

1. Run required commands to test all the code modified by this PR

# unit tests
# integration tests
# procs / testing logic

2. Further testing can be done by following the notes in TESTING-QA

Output:

Testing QA