fix bug where xcodeSubjectInfo.buildables isn't populated when using projects/schemes.

I fail.  This has been busted for a while.
fix crash when when running `analyze` with `-only`.

This fixes the bug @yiding noticed --

```
2013-08-29 14:09:57.074 xctool[63537:2507] -[Buildable objectForKeyedSubscript:]: unrecognized selector sent to instance 0x7ff3e3330a90

2013-08-29 14:09:57.210 xctool[63537:2507] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[Buildable objectForKeyedSubscript:]: unrecognized selector sent to instance 0x7ff3e3330a90'
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff984aab06 __exceptionPreprocess + 198
1   libobjc.A.dylib                      0x00007fff97bb13f0 objc_exception_throw + 43
2   CoreFoundationtion                      0x00007fff9854140a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3   CoreFoundation                      0x00007fff984aab069902e ___forwarding___ + 414
4   CoreFoundation 0x00007fff984aab069902ex00007fff98498e18 _CF_forwarding_prep_0 + 232
5   xctool                                0x000000010f1c33e3 -[AnalyzeAction performActionWithOptions:xcodeSubjectInfo:] + 557
6   xctool                              0x000000010f1c33e30010f1abd12 -[XCTool run] + 1967
7   xctool                               0x000000010f1aadfe main + 514
8   xctool                               0x000000010f1aabf4 start + 52
)
libc++abi.dylib: terminate called throwing an exception
```
remove accidental NSLog
in build.sh, retry builds if it looks like xcodebuild crashed.

We've seen both Xcode 4 and Xcode 5 crash while building xctool.  To
mitigate, we're wrapping our build in some retry logic.
bumping to 0.1.11
Show currently parallel running bundle

In case tests hang, we want to figure out which test is yet running.
This can hard when tests are run in parallel.

This patch updates the info when a bundle finishes.
Note that application tests will not be reported since they never
run in parallel currently. Anyway bundle name is added for the sake
of consistency.
fix EXC_BAD_ACCESS crash when running the xctool tests on 10.9

There was a place where we never bothered to call `-[NSTask init]`, and
it started to finally bite us on 10.9.
Save all exceptions raised in a test

By default SenTestRun will log every exception raised, not just the
first one. otest-shim will now send all exceptions to the reporters.
Note that often only the first exception is useful, so the reporters
continue to only display the first exception.
Split concept of test failures versus test errors

In the current version of xctool there is no separation of tests that
fail (an assertion fails) versus tests with errors (a non-assert
exception is thrown). This change splits non-passing tests into the two
catagories.

Note that since we now keep track of the number of passes manually
rather than rely on [SenTestRun testCaseCount] the total number of tests
reported will be the number of tests actually run, not the number of
tests configured. It could be argued that the test error count should
also include the number of tests configered but not run, but for now it
doesn't do that.
Emit output for all tests, even those that didn't get to run

Previously if a test or test suite crashed then none of the tests after
that one get to run. This means that the events never get outputted to
the reporters, and so they don't even know the tests exist. This causes
confusing results where a crash causes the existence of tests to be
hidden.

This commit fixes the situation with a bit of a architectual change.
OCUnitTestRunner becomes a reporter itself. As tests are executed it
tracks the state via the OCEventState subclasses. If at any point the
execution of a test suite fails we can use these state classes to emit
test events for the remaining tests and to handle any remaining events
that need to be emitted.