feat: Emit *.mjs files across all packages

[AbhiPrasad]

#10046

On the road of proper esm support, this first change introduces package.json exports to each of our packages. Now lets see what breaks 😭

This PR has some breaking changes or things that have been disabled to get the build working and tests passing which will need to be revisited later:

• The modulesIntegration uses require to get the module list and makes no sense for ESM
• Uses of require('inspector') or `dynamicRequire('inspector') have been replaced with regular imports. We can't use async import because it introduces async where it can't be supported. This change means we will break Vercel/pkg apps since they build Node without inspector. Vercel/pkg has been deprecated as of Jan 2024.
• nativeNodeFetchIntegration is no longer in the default integrations and the export has been removed for now. This integration uses require and when I tried import('opentelemetry-instrumentation-fetch-node') it seemed seemed to break Rollup output in a similar way to this: preserveModules creates wrong output rollup/rollup#3743

Other outstanding issues:

• Astro tests failing due to Error: Failed to resolve entry for package "https"

[timfish]

Node/Remix Integration tests are now passing. Still a few more issues to work through...

[timfish]

• Astro tests failing due to Error: Failed to resolve entry for package "https". The package may have incorrect main/module/exports specified in its package.json.
  • Weird since the module it's complaining about (https) is a Node built-in
  • @Lms24 A quick search suggests you've seen and fixed this error before! ([VIte/SvelteKit] Failed to resolve entry for package "https" vitejs/vite#12439)

[lforst]

@timfish We likely have to update the paths here:

sentry-javascript/packages/nextjs/src/config/loaders/wrappingLoader.ts

Line 18 in 4e28555

const apiWrapperTemplatePath = path.resolve(__dirname, '..', 'templates', 'apiWrapperTemplate.js');

[lforst]

The nextjs e2e test failures are weird. Next.js should not see the "wrapping target file" paths at all. They should all be bundled away with the rollup call here:

sentry-javascript/packages/nextjs/src/config/loaders/wrappingLoader.ts

Line 285 in 4e28555

rollup({

[Lms24]

@Lms24 A quick search suggests you've seen and fixed this error before! (vitejs/vite#12439)

IIRC my project's node_modules back then actually contained a strange npm package that was used instead of the builtin https package. Don't recall why this package was installed in the first place though

[timfish]

I've fixed this previous issue with nextjs which was caused by the build wrapping script being removed. This resulted in cjs templates being used rather than esm. The server tests are all now passing!

However, most of the client playwright tests are failing:

[timfish]

The global issue ended up being caused by #10925

[timfish]

Closing in favour of #10928