prunsrv failure doesn't trigger windows service recovery actions

This is directly related to DAEMON-244, which goes a long way towards solving the problem but still doesn't trigger Windows Service recovery actions correctly.

With that fix applied, when the Java process terminates abnormally prunsrv reports to the Windows Service Controller that the service had terminated and passes along the non-zero exit code from the app. However, actually notifying the service controller that the service has terminated at all (even with a non-zero exit code) prevents the recovery actions from kicking in.

From http://msdn.microsoft.com/en-us/library/ms685939(VS.85).aspx:
"A service is considered failed when it terminates without reporting a status of SERVICE_STOPPED to the service controller"

In order for the recovery actions to kick in, prunsrv should not notify the service controller at all when a failure is detected and should simply exit with a non-zero exit code.