IKEDA Sho

This also applies to `vertical_parameter_alignment_on_call` rule.

@dodikk Carthage/Carthage#622 is not related to static frameworks, that is about a “universal target” (_universal_ means the target can build both OS X and iOS platforms with selecting appropriate scheme)....

Another viewpoint: Deployment target settings of a generated Xcode project are not set for iOS, tvOS, and watchOS ([macOS is set to `10.10`](https://github.com/apple/swift-package-manager/blob/swift-3.1-branch/Sources/Xcodeproj/pbxproj().swift#L88-L93)). That means that the actual deployment target...

> When talking to the SwiftPM folks, this did seem like a potential issue. I'm not super knowledgable about it, but they mentioned the idea of passing an .xcconfig file...

`.xcframework` can be made by `xcodebuild -create-xcframework` which takes `-framework` and `-output` options. So that's means that we should run the command instead of `lipo`ing after building per-platform frameworks.

Looks like building Carthage itself with Xcode 11 (Swift 5.1) is a separate issue.

Switching to the the product of SwiftPM build and removing pkg releases may be good. Ref: #1559

I think `-enableThreadSanitizer NO` should be used which is documented in `man xcodebuild` instead.

It might be dupe of #493.

Finally submitted a fix https://github.com/Carthage/Carthage/pull/2125.