Explore AST-based module wrapping approach in Next.js

[lforst]

The current approach kinda works but has some issues:

• [nextjs] Default imports become undefined when using the SDK #8019
• Prisma Tracer not working on production builds #7216
• @sentry/nextjs autoInstrumentServerFunctions should not force all pages to use serverless functions #8323
• @sentry/nextjs + runtime = "edge" causes .next/app-build-manifest.json not to be populated and builds to break #8062
• Auto Instrumentation breaks Next.js edge API config (vercel region) #7450

I would like to explore using an AST-based approach to auto-wrap user modules, probably using the magicast package.

[lforst]

magicast uses optional chaining which is node 14+ so we prob can't use it (with reasonable effort).

[lforst]

Turns out most of these issues are not related. No "Five at one blow" situation here :(