feat: Inline @sentry/core dependency

[mydea]

This PR inlines the @sentry/core dependency into the build, moving it from dependencies to devDependencies.

The reason for this is to avoid shipping this dependency to users, as this may conflict with their own installed Sentry version.
Ideally, this should not really be a problem, but we have seen reports where package managers could not solve this issue nicely. So this is the "safer" solution, and also what we do at https://github.com/getsentry/sentry-javascript-bundler-plugins.

I played around a bit with unbuild and found this reference here: https://github.com/nuxt/nuxt/blob/f0ce20388d2ab533eba016de0565c150ea3c5172/packages/schema/build.config.ts#L23-L34, which I used as a basis for this. If unbuild were to be updated to 3.3.0+, this could be done via the new inlineDependencies config.

[mydea]

cc @AbhiPrasad maybe you can sanity check this!

[mydea]

For reference, we noticed this here: getsentry/gib-potato#237 and then "fixed" it here: getsentry/gib-potato#238 which shows the problem. I do not really believe this is a "bug" from this plugin here, as IMHO this should all work just fine, but somehow, apparently, some (?) bundlers just can't handle this nicely. 😬

[nicholas-codecov]

@mydea are you able to run pnpm install to update the lockfile, and add in a quick changeset minor for all packages?

Figured out how to do this myself 🤦