fix(nextjs): Connect Edge API route errors to span

[lforst]

Seems like through some weird behavior passing a scope function to captureException disconnects the active span from the error. This PR fixes this for Edge API routes in the Next.js SDK.

[AbhiPrasad]

We should investigate why this is happening.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.82 KB (+0.01% 🔺)
@sentry/browser - ES5 CDN Bundle (minified)	61.44 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.49 KB (+0.02% 🔺)
@sentry/browser - ES6 CDN Bundle (minified)	54.74 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	20.22 KB (0%)
@sentry/browser - Webpack (minified)	66.17 KB (0%)
@sentry/react - Webpack (gzipped + minified)	20.24 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	47.6 KB (0%)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.78 KB (+0.02% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	25.11 KB (-0.01% 🔽)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	43.11 KB (-0.82% 🔽)
@sentry/replay - Webpack (gzipped + minified)	38.45 KB (-0.99% 🔽)