feat(cloudflare): Fixed snippet to be cloudflare specific (#15369)

## DESCRIBE YOUR PR
A snippet was featuring Hono, but this is the cloudflare guide. Removed
the reference and updated the snippet to be correct for cloudflare.

Preview:
https://sentry-docs-git-fix-cloudflare-setup-snippet.sentry.dev/platforms/javascript/guides/cloudflare/#setup-for-cloudflare-workers

## 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 -->
- [x] 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)

---------

Co-authored-by: Shannon Anahata <[email protected]>

Author: sfanahata

docs/platforms/javascript/guides/cloudflare/frameworks/hono.mdx

@@ -40,7 +40,7 @@ The main Sentry configuration should happen as early as possible in your app's l
 
 <PlatformContent
   includePath="getting-started-config"
-  platform="javascript.cloudflare.workers"
+  platform="javascript.cloudflare.hono"
 />
 
 ### Migration from Community Middleware

platform-includes/getting-started-config/javascript.cloudflare.hono.mdx

@@ -0,0 +1,41 @@
+Wrap your Hono app with the `withSentry` function, for example, in your `index.ts` file, to initialize the Sentry SDK and hook into the environment:
+
+```typescript {filename:index.ts}
+import { Env, Hono } from "hono";
+import * as Sentry from "@sentry/cloudflare";
+
+const app = new Hono();
+
+// Add your routes here
+// app.get('/your-route', (c) => c.text('Hello!'));
+
+export default Sentry.withSentry(
+  (env: Env) => {
+    const { id: versionId } = env.CF_VERSION_METADATA;
+
+    return {
+      dsn: "___PUBLIC_DSN___",
+
+      release: versionId,
+
+      // Adds request headers and IP for users, for more info visit:
+      // https://docs.sentry.io/platforms/javascript/guides/cloudflare/configuration/options/#sendDefaultPii
+      sendDefaultPii: true,
+      // ___PRODUCT_OPTION_START___ logs
+
+      // Enable logs to be sent to Sentry
+      enableLogs: true,
+      // ___PRODUCT_OPTION_END___ logs
+      // ___PRODUCT_OPTION_START___ performance
+
+      // Set tracesSampleRate to 1.0 to capture 100% of spans for tracing.
+      // Learn more at
+      // https://docs.sentry.io/platforms/javascript/guides/cloudflare/configuration/options/#tracesSampleRate
+      tracesSampleRate: 1.0,
+      // ___PRODUCT_OPTION_END___ performance
+    };
+  },
+  app
+);
+```
+

platform-includes/getting-started-config/javascript.cloudflare.workers.mdx

@@ -1,7 +1,6 @@
 Wrap your worker handler with the `withSentry` function, for example, in your `index.ts` file, to initialize the Sentry SDK and hook into the environment:
 
 ```typescript {filename:index.ts}
-import { Hono, HTTPException } from "hono";
 import * as Sentry from "@sentry/cloudflare";
 
 export default Sentry.withSentry(
@@ -30,7 +29,11 @@ export default Sentry.withSentry(
       // ___PRODUCT_OPTION_END___ performance
     };
   },
-  // your existing worker export
-  app
+  {
+    async fetch(request, env, ctx) {
+      // Your worker logic here
+      return new Response("Hello World!");
+    },
+  }
 );
 ```