TraceServer: Add resetting to stop command error

Refine the error message for the stop command, adding an indication of
being about to reset. This hints the user about any next start command
being hopeful, despite this apparently failed stop.

This helps the case where VS Code/Codium exits without a clean server
stop. Exiting so does automatically stop the said server, but the code
that properly resets the internal workspace state is likely not reached
by that exiting act.

Theia Blueprint for that matter does properly reach that reset code,
upon exiting and having to auto-stop the server. And the third use case,
pertaining to PR #1's openvscode-server use, does rely on this workspace
state to stop a server started before reopening the browser client tab.

Contributes to fixing #8.

Signed-off-by: Marco Miller <marco.miller@ericsson.com>

Author: marco-miller

src/trace-server.ts

@@ -53,7 +53,7 @@ export class TraceServer {
                 },
                 async progress => {
                     progress.report({ message: 'Stopping...' });
-                    const message = prefix + ' stopping' + suffix;
+                    const message = prefix + ' stopping' + suffix + ' Resetting.';
                     treeKill(pid, error => {
                         if (error) {
                             this.showError(message);