fix: disable server bundle minification for readable error stack traces

[JorgeEscire]

References

• Fixes Production server clogs the logs on breaking exceptions #4124

Description

Disable minification for the server-side webpack bundle to produce readable error stack traces in production.

Instructions for Reviewers

List of changes in this PR:

• Added optimization: { minimize: false } to webpack/webpack.prod.ts to disable minification of dist/server/main.js

How to test:

1. Add throw new Error('hello world') anywhere in the body of server.ts to simulate an uncaught error
2. Rebuild with yarn build:prod
3. Start with yarn serve:ssr
4. Before this fix: The entire minified file gets printed to the log, making it impossible to determine what went wrong
5. After this fix: The stack trace shows the specific line where the error occurred, with readable code

Notes:

• The server bundle only runs on the server and is never sent to browsers, so minification provides no benefit
• mode: 'production' is preserved, so tree-shaking and other production optimizations remain active
• The browser bundle (webpack.browser.ts) is unaffected and remains minified

Checklist

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.

[alegontarz]

QA testing performed (no code review).

Works as expected:

1. After adding a test error in server.ts and running a production SSR build, the stack trace points to readable line numbers in dist/server/main.js instead of a single minified line.

[tinsch]

⚠️ @JorgeEscire @oscar-escire please take a look, this PR seems to be affected by the malicious bot code you mentioned in another PR.

[tdonohue]

Closing, as this PR is impacted by PolinRider malware.

⚠️ DO NOT DOWNLOAD OR RUN THIS PR until the attack code is removed.

@JorgeEscire and @oscar-escire : We can reopen this PR once it is cleaned up.