feat(nextjs): Parameterize prefix loader values

[lobsterkatie]

This changes the prefixLoader we use in the nextjs SDK to accept template name and replacement values as parameters, and pulls injection of that loader into a helper function. It also renames the current template from prefixLoaderTemplate to serverRewriteFramesPrefixLoaderTemplate, to better indicate its purpose and to distinguish it from future templates also using the prefix loader.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.57 KB (0%)
@sentry/browser - ES5 CDN Bundle (minified)	60.59 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.36 KB (+0.01% 🔺)
@sentry/browser - ES6 CDN Bundle (minified)	54.15 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	20.12 KB (0%)
@sentry/browser - Webpack (minified)	65.75 KB (0%)
@sentry/react - Webpack (gzipped + minified)	20.14 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	45.97 KB (0%)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.42 KB (+0.01% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	24.85 KB (+0.02% 🔺)
@sentry/replay index.js	37.08 KB (-0.33% 🔽)
@sentry/replay - Webpack (gzipped + minified)	37.06 KB (-0.32% 🔽)
@sentry/replay - Webpack (minified)	124.66 KB (-0.27% 🔽)

[lforst]

I am kinda starting to wonder whether our prefixLoader isn't just a glorified DefinePlugin but we can worry about that in the future.

[lobsterkatie]

I understand why you say that, but to be DefinePlugin, it'd need to be injecting values into code which already exists, which means we'd need to get users to include global.__rewriteFramesDistDir__ = '__DIST_DIR__'; in their sentry.server.config.js, which feels unlikely to work all that well.