Open Telemetry Monitoring integration with Google Cloud Trace API

### Version Information

Server Version: v2.23.0-cloud.1

### Environment

Cloud

### What is the current behaviour?

We're facing an error in the Open Telemetry Monitoring integration.
We're trying to send the project traces to the Google Cloud Trace API endpoint that is something like /v1/projects/{projectId}/traces but the Hasura Cloud client is trying to send those traces to /v1/traces endpoint instead, resulting in a 404 error. We also tried setting up a reverse proxy that expose /v1/traces endpoint and redirect the request to the correct endpoint but we still get the 404 error.

### What is the expected behaviour?

I'm expecting the Hasura Cloud client to send traces to the specified endpoint

### How to reproduce the issue?

1. From the https://cloud.hasura.io/projects screen go into project setting.
2. In the Integrations tab configure a new Open Telemetry integration with a working Cloud Trace API endpoint and the other required parameters.
3. Save the configuration and wait for the client trying to send the traces.

### Screenshots or Screencast

Example with Google Cloud Trace API endpoint:

Example with custom reverse proxy to the Cloud Trace API:

### Keywords

#cloud #monitoring #opentelemetry #googlecloudtrace

Start by tracing the OpenTelemetry integration configured from the Cloud project's Integrations tab and compare the configured Google Cloud Trace endpoint with the emitted /v1/traces request. Reproduce the setup against the Google Cloud Trace API; done when traces reach the specified endpoint without 404 errors.

Written by the indexing model from the issue text.