feat(nuxt): Respect user-provided source map generation settings

[s1gr1d]

Nuxt implementation for: #13993
Fixes: #13997

In Nuxt, there are 3 places to set source maps (and all need to be enabled):

• sourcemap
• nitro.rollupConfig.output.sourcemap
• vite.build.sourcemap

As Nuxt sets sourcemap.client: false (docs here), it's not possible to determine whether this setting was set by the user or the framework. Users have to set this manually like this:

export default defineNuxtConfig({
  sourcemap: {
    client: true,
  },
})

With this PR, all source maps are set to 'hidden' if they were undefined before and keep the setting otherwise. This is done in 3 separate functions (one for vite, rollup and nuxt) to better distinguish between the settings.

[chargome]

LGTM

[chargome]

Suggested change

	* Setup source maps for Sentry inside the Nuxt module during build time (in Vite for Nuxt and Rollup for N itr/**
	* Setup source maps for Sentry inside the Nuxt module during build time (in Vite for Nuxt and Rollup for Nitro)

[s1gr1d]

oh noo that is left from biome (in WebStorm), it continuously messed up this file 😢 Especially in JSDoc and function declarations.

[chargome]

Suggested change

	- keep this setting this and
	- keep this setting and

[chargome]

l: the logic in here is basically the same for vite rollup and nuxt, maybe this could be moved into a function instead

[s1gr1d]

I thought about that as it would make the code eventually shorter. But I kept the three different functions (and so the duplication) because I think it adds more complexity if those functions are combined into one. The log outputs and the sourcmap option source are different for vite, rollup and nuxt and a function abstraction would make it very difficult to read. I think it's better to have some duplication here for the purpose of readability.

[chargome]

l: some vars use sourcemap camel-cased, others not

[s1gr1d]

Changed all variables/comments to "source maps" and sourceMap according to https://tc39.es/source-map/