[Next.js] Support setting different options for different runtimes (browser/server/edge)

[lforst]

Originally posted by @ricardomatias in discussions:

I've removed the sentry.edge.config.ts and sentry.server.config.ts and I still get sourcemaps for both of them. I only want client sourcemaps.

I don't think this is possible right now without some very ugly hacks. We should provide some way of setting different options for the different runtimes.

Idea No.1 and probably my favorite: Allow for the sentryBuildOptions argument in withSentryConfig to be a function/callback that receives the runtime as an argument. (probably should pass it within an object so that we can extend it in the future)

[mydea]

@chargome do you have any details on this?

[chargome]

Have not yet looked into this yet, but seems like a good idea to be able to modify build options per runtime. Could also cut down build time if people want to use sentry client only.

[kylemh]

I'm wondering what my options are for self-hosted too. There's no point to edge config for me, correct? If excluded, does it negatively affect anything?