fix(nextjs): Await Next.js server in patched getServerRequestHandler

[lforst]

Fixes #6059

Attempts to fix a bug where we try to grab the prototype of the Next.js server even though it hasn't been created yet. I couldn't repro this locally - I think this might be due to a race condition.

I believe (emphasis on "believe") it is safe to call getServer inside of the getServerRequestHandler function because Next.js itself calls it in there: https://github.com/vercel/next.js/blob/0beed3563cdab846fd6b683f1ed5586de3e7d96d/packages/next/server/next.ts#L175

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.5 KB (-0.01% 🔽)
@sentry/browser - ES5 CDN Bundle (minified)	60.35 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.12 KB (-0.03% 🔽)
@sentry/browser - ES6 CDN Bundle (minified)	53.68 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	19.86 KB (-0.02% 🔽)
@sentry/browser - Webpack (minified)	65.09 KB (0%)
@sentry/react - Webpack (gzipped + minified)	19.89 KB (-0.01% 🔽)
@sentry/nextjs Client - Webpack (gzipped + minified)	45.75 KB (-0.01% 🔽)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.22 KB (-0.02% 🔽)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	24.6 KB (-0.01% 🔽)

[AbhiPrasad]

poked through the source code and this look safe 🤞

[kachkaev]

Glad to see this fix merged! What’s your typical ETA to release? Just curious, working on blockprotocol/blockprotocol#692 🙃

[lforst]

Soon TM