refactor(nextjs): Change ESM interop. to remove lazy loading

[timfish]

Code checking default like this always points to an ESM/CJS interop issue:

sentry-javascript/packages/server-utils/src/orchestrion/bundler/webpack.ts

Line 53 in 8c6358a

const codeTransformerWebpack = mod.default ?? (mod as unknown as NonNullable<typeof mod.default>);

This is caused by our repo-wide Rollup setting of interop: 'esModule'. This is required for us to be able to monkey patch Node built-ins but causes the above issues with CJS dependencies that use the classic CJS default export (module.exports = fn).

This PR overrides the interop setting for the suspect package and removes the lazy dependency loading.

[JPeer264]

Haven't tested if that changes anything. But it sounds valid.

I think we should wait for @chargome though

[timfish]

Practicing what I preach 🤣

• apm-js-collab/code-transformer-bundler-plugins@d133878

[sentry]

Bug: The function sentryOrchestrionWebpackPlugin is called without arguments, but its options parameter no longer has a default value, leading to a TypeError when options.instrumentations is accessed.
_{Severity: HIGH}

Suggested Fix

Restore the default value for the options parameter in the sentryOrchestrionWebpackPlugin function signature. Change (options: PluginOptions) to (options: PluginOptions = {}) to prevent options from being undefined when the function is called without arguments.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: packages/server-utils/src/orchestrion/bundler/webpack.ts#L50

Potential issue: The function `sentryOrchestrionWebpackPlugin` is called without
arguments from `packages/nextjs/src/config/webpack.ts`. A recent refactor removed the
default `{}` value for the `options` parameter. Consequently, `options` becomes
`undefined` inside the function. This `undefined` value is passed to
`orchestrionTransformOptions`, which then attempts to access `options.instrumentations`,
causing a `TypeError`. This will crash the webpack build process for Next.js
applications that have the `_experimental.useDiagnosticsChannelInjection` option
enabled.

Also affects:

• packages/nextjs/src/config/webpack.ts:436~436

_{Did we get this right? 👍 / 👎 to inform future reviews.}