feat: Move LinkedErrors integration to @sentry/core

[AbhiPrasad]

• Remove LinkedErrors from Node SDK and use Core SDK LinkedErrors instead
• Use LinkedErrors integration in Vercel Edge SDK
• Update Deno SDK to use LinkedErrors integration from Core instead of Browser

In a future PR I'm going to remove browser specific LinkedErrors integration and make everything rely on implementation in Core SDK.

This refactor came from two places

1. We noticed the Deno SDK relies on the browser SDK. This is not ideal, so this helps with that
2. We got feedback via customer that LinkedErrors was not available in @sentry/vercel-edge

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	77.43 KB (0%)
@sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped)	66.49 KB (0%)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	30.97 KB (0%)
@sentry/browser - Webpack (gzipped)	21.29 KB (0%)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	67.79 KB (+0.19% 🔺)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	29.09 KB (+0.45% 🔺)
@sentry/browser - ES6 CDN Bundle (gzipped)	21.23 KB (+0.48% 🔺)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	216.85 KB (+0.21% 🔺)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	88.28 KB (+0.5% 🔺)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	63.28 KB (+0.7% 🔺)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.8 KB (+0.19% 🔺)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	77.82 KB (0%)
@sentry/react - Webpack (gzipped)	21.34 KB (0%)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	94.15 KB (0%)
@sentry/nextjs Client - Webpack (gzipped)	47.86 KB (0%)

[Lms24]

Makes sense to me!
(also I'm wondering why we had different integrations for browser and Node in the first place)