Prisma tracing

[Cold-A-Muse]

In this PR

Implemented the new built-in tracing functionality of prisma using jaeger.

**Changes: **

• Introduced a new JAEGER_TRACING_ENDPOINT env variable to api env (default: http://localhost:14268/api/traces)
• Added a new jaeger tracing service to our docker-compose
• Upgraded prisma to latest release (4.4.0)

Follow up:

• jaeger UI is served on port 16686. I reckon we need to put some sort of password security on this port so others can't peek at our performance.
• By default, jaeger starts with memory storage, meaning ‼️ it will lose all data upon restart‼️. Jaeger recommends storing data in Elasticsearch (as per https://www.jaegertracing.io/docs/1.38/faq/#what-is-the-recommended-storage-backend)

FIXES HAAS-444

[linear]

HAAS-444 Prisma: OpenTelemetry and Tracing

Description

We should investigate https://www.prisma.io/blog/tracing-tutorial-prisma-pmkddgq1lm2 and see whether we can enable Prisma's tracing, and use it.

[aws-amplify-eu-central-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-477.d36c61y3h9mqcx.amplifyapp.com

[aws-amplify-eu-central-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-477.d2j37lx5gsfgp1.amplifyapp.com