fix(nextjs): Don't use chalk in turbopack config file (#17806)

We don't know yet why but this config code seems to be evaluated once at
runtime for some users when using turbopack. The chalk import breaks
with `Failed to load external module @sentry/nextjs: Error
[ERR_REQUIRE_ESM]`.
Just getting rid of this import for now to not break apps.

We're still investigating together with Vercel why this this code gets
pulled in.

closes #17691

Author: chargome

packages/nextjs/src/config/turbopack/constructTurbopackConfig.ts

@@ -1,5 +1,4 @@
 import { debug } from '@sentry/core';
-import * as chalk from 'chalk';
 import type { RouteManifest } from '../manifest/types';
 import type { NextConfigObject, TurbopackMatcherWithRule, TurbopackOptions } from '../types';
 import { generateValueInjectionRules } from './generateValueInjectionRules';
@@ -57,9 +56,7 @@ export function safelyAddTurbopackRule(
   // If the rule already exists, we don't want to mess with it.
   if (existingRules[matcher]) {
     debug.log(
-      `${chalk.cyan(
-        'info',
-      )} - Turbopack rule already exists for ${matcher}. Please remove it from your Next.js config in order for Sentry to work properly.`,
+      `[@sentry/nextjs] - Turbopack rule already exists for ${matcher}. Please remove it from your Next.js config in order for Sentry to work properly.`,
     );
     return existingRules;
   }