Fix CONFIG_START/CONFIG_END under XCTest

Sets up KWConfigurationTestObserver in +[KWExampleSuiteBuilder initialize] to
respond to -[XCTestObserver startObserving] and -[XCTestObserver stopObserving].

Also moves TestSuiteConfigurationAdditions into the SenTestingKit subdirectory,
and removes it from the XCTest static lib, to disable the method swizzling
implementation under XCTest.
Add missing calls to super
Add beforeEachSpec and afterEachSpec blocks
Correctly register KWConfigurationTestObserver as XCTestObserverClass

There is a timing issue when setting the `XCTestObserverClass` default via
`setObject:forKey:` -- when called from `+load`, XCTest's own startup overrides
the value that was set, and when called from `+initialize` it seems to be too
late for XCTest to actually use the value (i.e., it's already created
observers).

Turns out, XCTest actually respects a default for `XCTestObserverClass` set in
`NSRegistrationDomain`. This means that the defaults registration can be moved
into `+load`, ensuring it happens before XCTest sets up observers.
Revert "Revert pull request #427."

This reverts commit 503f7e0638bc4cdcd9994242e6aa95303baa04c6.
Merge branch 'revert-revert' into config-fixes
Support XCTest under Xcode 6 Beta 2
Apply FRAMEWORK_SEARCH_PATHS fixes to OSX targets and project file
Merge branch 'master' of github.com:kiwi-bdd/Kiwi into config-fixes

Conflicts:
	Classes/Core/KWSpec.h
	Kiwi.podspec
	Kiwi.xcodeproj/project.pbxproj
	KiwiXCTests/KWXCFunctionalTest.m
	SenTestingKit/SenTestSuite+KiwiAdditions.m
Merge branch 'xcode6'

Fixes #543. Closes #540, #544.
Implement before/after all specs hooks by swizzling +[XCTestSuite testSuiteWithName:]

The XCTestObserver implementation of beforeAllSpecs/afterAllSpecs wasn't
stable. At various times the hooks would run from within the Kiwi
project, or from an external test suite, but usually not from both, and
it was never clear what caused it to work or not. Setting values in
NSUserDefaults at load time doesn't seem to be a stable strategy.

This implementation swizzles +[XCTestSuite testSuiteWithName:] and looks
for a suite named "All tests". It then dynamically sets the class of the
"All tests" suite to be a custom subclass that overrides setUp and
tearDown to call KWSuiteConfigurationBase.

Also adds an integration test step in the Makefile that looks through
the xcodebuild.log output for the strings "beforeAllSpecs" and
"afterAllSpecs" as an indication that the config hooks were executed
(logged from Tests/Config.m).

Finally, the beforeEachSpec and afterEachSpec have been removed from the
public interface of KWSuiteConfigurationBase as they are still
unimplemented.
Remove defunct macros from KiwiConfiguration.h
Merge pull request #475 from sharplet/config-fixes

Fix CONFIG_START/CONFIG_END
Merge remote-tracking branch 'origin/master' into let-futures

Conflicts:
	Kiwi.xcodeproj/project.pbxproj
Move let functional tests into Tests/KWLetFunctionalTests.m
Add (failing) functional test describing use of future strings in expectations

When futures are involved, it seems that -isEqual: is not necessarily
commutative. For example, these two aren't guaranteed to be equivalent:

    [[futureObject should] equal:actualObject];
    [[actualObject should] equal:futureObject];

In the case of string comparison, it is the second form that fails. An
MAFuture is very lightweight proxy for the resolved future value --
almost all messages the future receives are forwarded to the real object
it represents. However when a future string is on the right-hand side of
-isEqual:, the comparison fails. My best guess is that the
implementation of -isEqualToString: doesn't send any messages to the
right operand, and accesses its internal storage directly.