feat: allow disabling sourcemap generation

[danielroe]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR disables sourcemap generation for our various transform plugins when building. (I would also be open to adding a build.sourceMap option that allows configuring sourcemap generation.)

I've seen one or two reports of memory issues when building, and have previously resolved this with turning off magic string sourcemaps. For context:

• Rollup build chugs memory when site has a lot of components bridge#151
• Plugin replace chugs a lot of memory rollup/plugins#1064
• [enhancement] Generating sourcemap via magic-string triples memory usage in most applications Rich-Harris/magic-string#195

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	79b2733
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6262c86e5071ad0009fb013a

[pi0]

Do you have any context of the source map memory leak issue? It can happen when enabling development too and we can't just mask the issue this is a nice feature for production build too.