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

[Tanker187]

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

In general, the fix is to stop returning the stack trace in the HTTP response body. Instead, log the full error details on the server (using console.error or a logging library) and send the client a generic message and/or a simple error page with status code 500.

For this specific code, the minimal change without altering existing behavior too much is:

• Keep calling vite.ssrFixStacktrace(e) to preserve source-mapped stack traces for debugging.
• Replace console.log(e.stack) with a more appropriate server-side log (e.g., console.error(e.stack || e)).
• Replace res.status(500).end(e.stack) with a generic error response such as res.status(500).end('Internal Server Error'). This preserves the status code and avoids exposing the stack trace.

All changes are confined to the catch block in playground/ssr-html/server.js. No new imports or external methods are required; basic console.error is sufficient.

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