update the script to handle crashed app/tests but XCUnit continues...

[mikelupo]

If a test starts, but does not complete, hence there is no Test Case "error", "failed" or "passed" stanza to matched the "started" stanza, then OCUnit2Junit would not report this errant test. If XCUnit continues to run (as it sometimes will do) then the test failure will be ignored. If all further downstream tests have passed, then then the build may get reported as stable, when otherwise it should not. This PR hopefully deals with that.

Note, that we also are counting the errors now, but in the case where a test has an error and a failure, it's double counted as an error and a failure. @ciryon Can you please review that part of the code with extra scrutiny?

Thanks@