🚀 Enhancement: Open Telemetry Endpoint

### 🔖 Enhancement description It would be amazing if there was an endpoint on Appwrite to collect Open Telemetry data (https://opentelemetry.io/docs/). This would highly bolster the ability to trace problems and log activity on apps and services. It could possibly be used to create feature parity with Firebase Crashalytics. ### 🎤 Pitch The best way to do this would be to implement a collector into the REST api (https://opentelemetry.io/docs/collector/). This would then be able to organize the traces and logs into the connected database behind the Appwrite instance. This would allow an easy view in the console of the logs and traces, but more importantly mean that the existing REST and GraphQL infrastructure inside Appwrite can be leveraged to view and search logs and traces. This would also prevent apps from having to implement a direct db connection in open telemetry that circumvents the Appwrite interface. It's far cleaner and safer/secure for an app to only talk to Appwrite to read/write data. Currently, any logging or crash monitoring solution requires a second connection to another database OR a second database inside Appwrite . ### 👀 Have you spent some time to check if this issue has been raised before? - [X] I checked and didn't find similar issue ### 🏢 Have you read the Code of Conduct? - [X] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)