How should I properly to handle CORS preflight requests when initializing the Genesys Cloud Web Messaging SDK inside a Next.js 14 application using the App Router? I am encountering a 403 Forbidden error specifically on the OPTIONS request for https://api.mypurecloud.com/api/v2/organizations/{orgId}/messaging/channels during the initial handshake. The error payload indicates Access-Control-Allow-Origin header is missing, despite the domain being whitelisted in the Genesys UI. I am using the @genesys/web-messaging-sdk package and initializing it in a client component as follows: const initMessenger = () => { messenger.init({ organizationId: process.env.NEXT_PUBLIC_GENESYS_ORG_ID, apiHost: process.env.NEXT_PUBLIC_GENESYS_API_HOST, ... }); };. The issue persists even after adding a custom _next/data middleware to forward headers. Is there a specific configuration required in the messenger.init object or the Genesys Channel settings to bypass this preflight block for server-side rendered environments? I have verified the token generation via /api/v2/authorization/token works correctly, but the widget fails to mount due to this network error.