After the fix for #2696 I've observed (on Windows) regression in the
JUnit view: if the test was terminated (regularly) very fast, the test
results would be sometimes not shown at all, and JUnit view would show
"Stopped" status.

I see (at least on Windows) that test launch termination is reported
almost immediately, *before* any test process output is processed by
ServerConnection.

The correct place to evaluate "stopped or not" condition would be after
the output processing is finished, so moved the new block of code
from #2696 to the ServerConnection.shutDown().

See https://github.com/eclipse-jdt/eclipse.jdt.ui/issues/2696