feat: add OpenTelemetry with OTLP exporter

[damienpontifex]

• Resource with default service name
• OTLP exporter that will use standard environment variables for configuration
• FastAPI auto instrumentation for app
• Adds a docker compose setup for validating the tracing with docker compose up -d --build and Grafana LGTM stack for viewing/inspecting the traces. Screenshot below

Issue resolved by this Pull Request:
Resolves #357

[github-actions]

✅ DCO Check Passed

Thanks @damienpontifex, all your commits are properly signed off. 🎉

[dosubot]

Related Documentation

Checked 2 published document(s). No updates required.

^{How did I do? Any feedback?}  

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

[dolfim-ibm]

@damienpontifex Otel could be used also for telemetry such as response time dashboard, etc, right? do you have any example how this would look like?

[damienpontifex]

@dolfim-ibm 💯
In the example/screenshot above, I'm using Grafana, so to follow on with that, here's a good overview of a lot of things you can do with Otel traces/metrics out of the box https://grafana.com/products/cloud/application-observability/
This would be valid for any Otel backend e.g. I've also used azure app insights, dynatrace etc etc, it's all capable of doing the washboarding like you say using Otel data