As notified in #10384, we were missing quite a few exports in the Remix SDK. I fixed a couple of them in #10385 but wanted to do a proper audit of other SDKs where we have the same potential problem.

As a result, this PR introduces an e2e test that checks if all @sentry/node exports were re-exported in packages that depend on @sentry/node. It's not a real e2e test, as there's no actual test application, but we only execute a script that imports various SDKs depending on @sentry/node. However, IMO it makes a lot of sense to test the export of the final tarballs which we already have the infrastructure for in our e2e tests.

Some remarks:

• Of course there are special cases around what actually should be re-exported. The test script allows to handle this on a global, as well as dependent-specific basis.
• Limitation: We only test top-level exports for now (IMO this is enough).
• Limitation: We only test ESM (I think; again probably good enough)
• Limitation: Bun doesn't work yet, still looking into it (might fix in a follow-up PR)

Example of failing CI job:

Background:

For reasons unknown to us, rollup seems to bundle export * from "@sentry/node" statements into the default property of higher level SDKs. Therefore we have to individually re-export APIs from @sentry/node in each SDK depending on the Node package. This has a lot of potential for unintended export inconsistencies.

I'm still skipping some packages on purpose as these currently actually still have missing exports. Will fix them in follow-up PRs and opt them in to this test. Decided on this order because this makes my decisions clearer as to what we actually re-export in the packages.