fix: capture and highlight stderr output from dspublisher process

[tomivirkki]

Summary

• Add stderr listener to capture console.warn and console.error output from spawned dspublisher process
• Highlight stderr output in red color for better visibility

Problem

When running npm run dspublisher:start, console warnings and errors from the dspublisher process were not visible because the script only listened to stdout. Since console.warn and console.error write to stderr, this output was being lost.

After the change:

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

AI Language Review

• In the TypeScript file, the word "Plase" is misspelled, and should be corrected to "Please" in the error message for checking if Maven is installed. Adjust the message to avoid duplicating the same error handling function for ps.on('error', ...).

• The execute function now includes handling for standard error output (ps.stderr.on('data', ...)). Ensure that any relevant error messages from this change are correctly logged in red color as intended.