Run tests on Windows
Check for child_process.exec() error events & output the failure string

If the child_process.exec() call fails entirely (eg spawn ENOENT due to
not having the command interpreter on the PATH), then the child_process
'exit' event is never fired - so prior to this patch nothing would have
been output and the command would appear to complete successfully.

With this patch the task correctly returns as failing and something
similar to this output to the grunt error log:
>> child_process.exec() failed with: Error: spawn ENOENT

This should avoid the confusion seen in:
https://github.com/jharding/grunt-exec/issues/47
Update message outputed for error.
0.4.6
Drop ci for node 0.8.