Potential fix for code scanning alert no. 48: Information exposure through a stack trace

[Tanker187]

Potential fix for https://github.com/Tanker187/vite/security/code-scanning/48

In general, the fix is to avoid exposing stack traces to clients while still logging them on the server. The catch block should log e.stack (or the full error object) using console.error or a logging library, and then return a generic 500 error message without stack details.

Concretely, in playground/ssr-noexternal/server.js, within the catch (e) block inside app.use('*all', async (req, res) => { ... }), we should:

• Keep the dev-only vite.ssrFixStacktrace(e) call.
• Replace console.log(e.stack) with console.error(e.stack || e) to better indicate an error.
• Replace res.status(500).end(e.stack) with a generic message, for example res.status(500).end('Internal Server Error') (or a similarly vague phrase).
  No new imports or helper methods are strictly required for this change, and existing functionality (rendering behavior, logging for debugging) is preserved while avoiding stack trace exposure.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.