chore(config): defer Cloudflare initialization to development only

Wrap OpenNext Cloudflare initialization in development check and use dynamic import to prevent execution in non-dev environments. This resolves potential issues with the initialization running in production builds.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: ericyangpan

next.config.ts

@@ -172,6 +172,9 @@ const withMDX = createMDX({
 export default withNextIntl(withBundleAnalyzer(withMDX(nextConfig)))
 
 // added by create cloudflare to enable calling `getCloudflareContext()` in `next dev`
-import { initOpenNextCloudflareForDev } from '@opennextjs/cloudflare'
-
-initOpenNextCloudflareForDev()
+if (process.env.NODE_ENV === 'development') {
+  // eslint-disable-next-line @typescript-eslint/no-floating-promises
+  import('@opennextjs/cloudflare').then(({ initOpenNextCloudflareForDev }) => {
+    initOpenNextCloudflareForDev()
+  })
+}