Fix Implicitly Unwrapped nil value error in `XcodeSpec` using Optional NSString

<i>Related to #206</i>
<i>Refactor of #209</i>

When running `otool` in `XcodeSpec`, [the `value` of the `first` of the stream is implicitly unwrapped](https://github.com/Carthage/Carthage/blob/9368c474f195c91ac7d4b5c1ee3150bacec67f36/CarthageKitTests/XcodeSpec.swift#L74-77).

But, if `otool` hits an error, then `first()` returns a `.Failure`, whose `value()` returns `nil`, leading to `fatal error: unexpectedly found nil while unwrapping an Optional value`.
Instead of the if statement and optional, could we just append `?? ""` onto this expression? Then it’ll avoid implicitly unwrapping, we won’t have to explicitly unwrap, we won’t have to provide an explicit type, and the expectations will fail safely for the `nil` case.