feat(node-profiling): Output ESM and remove Sentry deps from output

[timfish]

• Moves Sentry deps to dependencies rather than devDependencies
• Updated package.json exports
• Updated the rollup config to mirror our other modules with the addition of the commonJs plugin
• I couldn't use createRequire myself because Jest can't handle import.meta so instead I used @rollup/plugin-esm-shim which shims both require and __dirname in cpu_profiler.ts in the ESM output!

[AbhiPrasad]

Little scared about edge cases with bundling, but lets see how it goes!

[JonasBa]

Eghhh, I dont think this will work, but lets see. The reason is that ESM doesnt know what to do with .node modules by default whereas CJS does, and it's unclear here if the require shim uses the CJS loader or not, if it does then this will work, else it'll break with unknown module/configure loader message.

Afaik what others do is they ship the equivalent of our cpu_profiler.ts or the one file in the source which actually imports the bindings as CJS, which means that 99% of the application is ESM, but then when you need to load the bindings, you force CJS so that the loader knows how to properly open it. Lets see how well this works, I'd be interested to see if it works

[timfish]

We could always add another export @sentry/profiling-node/cjs which points at the cjs output and can be used if your bundler can't handle our ESM output?

Or alternatively output cpu_profiler.cjs so that file is call CommonJs.