Prevent JS sources minification in debug

[ilonatommy]

I believe npm run build should not minify js files that it's producing in src\Components\Web.JS\dist\Debug . That's why we're using debug mode. There's a lot of hassle with debugging the minified files now or having to look for the place in rollup to disable minification.

Description

• do not minify for dist\Debug
• keep minifying for dist\Release

Before this change:
both dist\Debug and dist\Release had same, minified contents.

Use case:

Replacing packages in user's repro app with the current packs from the repo.

This is just a proposal and should be discussed if there is some real reason why we chose to minify in debug.

[Copilot]

Pull Request Overview

This PR prevents JavaScript source minification when building in debug mode by conditionally applying the Terser plugin based on the environment. The change ensures that debug builds produce unminified JavaScript for easier debugging, while release builds continue to use minification for optimization.

• Conditionally applies Terser minification plugin only in non-development environments
• Improves debugging experience for development builds

[ilonatommy]

A workaround way from @javiercn:

loading the source maps manually to the browser, following https://developer.chrome.com/docs/devtools/developer-resources.