Fix broken url interpolation (#15391)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR

This is a fix for the code snippets that are just rendering strings, e.g
`___VERCEL_LOG_DRAIN_URL___`

This issue was caused by a client/server mismatch and how the code block
children are structured without a language specification. A single text
node just renders the string. The other refs work because when there's
other text in the code block, the structure works as expected.

Just needed to add a language keyword for things to align.

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

Co-authored-by: Michi Hoffmann <cleptric@users.noreply.github.com>

Author: jaffrepaul

docs/product/drains/integration/cloudflare.mdx

@@ -28,7 +28,7 @@ To configure your logs destination, click **Add destination** and configure the
 2. Destination Type: Select Logs
 3. OTLP Endpoint: Your Sentry OTLP logs endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/logs`)
 
-```
+```bash
 ___OTLP_LOGS_URL___
 ```
 
@@ -50,7 +50,7 @@ To configure your traces destination, click **Add destination** and configure th
 2. Destination Type: Select Traces
 3. OTLP Endpoint: Your Sentry OTLP traces endpoint (e.g., `https://{HOST}/api/{PROJECT_ID}/integration/otlp/v1/traces`)
 
-```
+```bash
 ___OTLP_TRACES_URL___
 ```
 

docs/product/drains/integration/vercel.mdx

@@ -47,7 +47,7 @@ After selecting the Logs data type, you'll need to configure the drain to send d
 4. Select which environments to drain from. You can choose to drain from all environments or select specific ones.
 5. Under the custom endpoint tab add the Sentry Vercel Log Drain Endpoint in the URL field. You can find the endpoint in your [Sentry Project Settings](https://sentry.io/settings/projects/) under **Client Keys (DSN)** > **Vercel**. You can select either JSON or NDJSON encoding.
 
-```
+```bash
 ___VERCEL_LOG_DRAIN_URL___
 ```
 
@@ -67,7 +67,7 @@ After selecting the Traces data type, you'll need to configure the drain to send
 2. Configure the sampling rate to control the volume of data sent to your drain. We recommend sampling 100% of the data to ensure you get all the data you need.
 3. Under the custom endpoint tab add the Sentry Vercel Log Drain Endpoint in the URL field. You can find the endpoint in your [Sentry Project Settings](https://sentry.io/settings/projects/) under **Client Keys (DSN)** > **OpenTelemetry (OTLP)** under the **OTLP Traces Endpoint** section.
 
-```
+```bash
 ___OTLP_TRACES_URL___
 ```