feat: added setup for production observability (metrics via OTEL)

[sheensantoscapadngan]

Description 📣

This PR adds instrumentation with OpenTelemetry with support for exporting to prometheus or to an OTLP endpoint.

The dev setup includes the following components:

• Open Telemetry (for instrumentation and gathering of application traces and metrics)
• Open Telemetry collector (for batching of telemetry data from application servers and for exposing data for long-term storage)
• Prometheus (for storage of metrics in time-series format)
• Grafana (for visualization of time-series data from Prometheus)

Documentation update:

Type ✨

• Bug fix
• New feature
• Breaking change
• Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[gitguardian]

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9387833	Triggered	Generic Password	0693f81	prometheus.yml	View secret
9387833	Triggered	Generic Password	33b49f4	docker-compose.dev.observable.yml	View secret
9387833	Triggered	Generic Password	33b49f4	docker-compose.dev.observable.yml	View secret
9387833	Triggered	Generic Password	fc3a409	prometheus.yml	View secret
9605380	Triggered	Generic Private Key	a6137f2	backend/e2e-test/routes/v3/secrets-v2.spec.ts	View secret
9605380	Triggered	Generic Private Key	a6137f2	backend/e2e-test/routes/v3/secrets-v2.spec.ts	View secret
9387833	Triggered	Generic Password	d71c85e	docker-compose.dev.observable.yml	View secret
9387833	Triggered	Generic Password	d71c85e	docker-compose.dev.observable.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[maidul98]

Good setup, left some questions and comments

[maidul98]

looks good, just two small nits. also please add a run buck for setting this up locally in a runbook