Update underlying invocation of `xcodebuild -showBuildSettings` such that iOS Test Bundle Schemes function normally under Xcode 5.x. fixes #187

This change fixes test execution failures under Xcode 5 with the error message: `ERROR: Expected to receive build settings for 1 target`

* Add utility methods for introspecting the version of xcodebuild that xctool is interacting with
* Use the `test` action when introspecting the test environment under Xcode 5.x
* Use the `build` action when introspecting the test environment under Xcode 5.x
moving ArrayContainsSubsequence into a TestUtil so we can share.
change XcodebuildVersion() to use DTXcode from Xcode's Info.plist
XcodeSubjectInfo: attempt to fetch build settings from multiple actions.
setting ORGANIZATIONNAME = "Facebook, Inc."
set LastUpgradeCheck = 0500;
removing old 'Run Script' steps needed for Xcode 4 unit testing.
dont_clang_as_osx: fix the issue where Xcode couldn't discover stuff.

This fixes the problem we were seeing in build.sh:

```
2013-11-01 14:10:35.062 xcodebuild[24282:4f1b] error: Error Domain=NSPOSIXErrorDomain Code=2 "Non-zero exit code 1 returned from shell command:
/Users/fpotter/xctool/otest-query/../Configurations/dont_clang_as_osx.py -v -E -dM -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -x objective-c -c /dev/null 2>&1" UserInfo=0x7fd59006d5c0
{NSLocalizedDescription=Non-zero exit code 1 returned from shell
command: /Users/fpotter/xctool/otest-query/../Configurations/dont_clang_as_osx.py -v -E -dM -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -x objective-c -c /dev/null 2>&1, NSLocalizedFailureReason=No such file
or directory}
2013-11-01 14:10:35.063 xcodebuild[24282:4f1b] Warning:  Couldn't discover the 'dont_clang_as_osx.py' compiler's built-in search paths and preprocessor definitions for language dialect 'objective-c'.
Compiler: /Users/fpotter/xctool/otest-query/../Configurations/dont_clang_as_osx.py
Reason: /Users/fpotter/xctool/otest-query/../Configurations/dont_clang_as_osx.py -v -E -dM -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -x objective-c -c /dev/null 2>&1
```
moving build scripts under a new 'scripts' dir.

I'm going to be adding to these, and don't want to clutter up the root
anymore.
link ROOT/xctool.sh -> ROOT/scripts/xctool.sh
scripts/build_settings.include generates the common build settings

We can then use this from build.sh and make_release.sh
update .travis.yml to point at scripts/build.sh
removing XCUnsuppressExpectedAssertionFailures() - it's not used
fixing analyzer warning in JUnitReporter ...

... but, while I'm here, let's kill all the error-prone manual memory
management.
some JUnitReporter cleanup

* reducing the amount of configusin, almost shadowing going on.  e.g.,
  variables called 'testSuites' and 'testsuites'
* line wrapping some long lines
* more subscripting for dictionary access instead of objectForKey:
silence over-release warning in OCUnitTestQueryRunner

The analyzer wasn't recognizing that `createTaskForQuery` returns a +1
retain count instance, despite the fact that it had a create* prefix.
This silences it.
fix 'Potential leak of an object stored into 'resultBuilder'

If we just autorelease at the top, all is fine.
fixing a bunch of tests that were leaking objects.
splitting ContainsException.h into a .h and .m

It worked fine before, but would prefer to have these separate.
ContainsException -> ContainsAssertionFailure

... so it matches the class name within.