Ensure private headers are declared as such in a framework's generated module map.

[Spec|Doc|Fixture] Cleanup in preparation to a fixed xcasset handling

Update LICENSE

Update LICENSE

Added emails

Update LICENSE

Update cocoapods.gemspec

Update LICENSE

Update LICENSE

Whenever I run `pod install` I get warnings like:

```
[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `TestClient` to `Pods/Target Support Files/Pods-TestClient/Pods-TestClient.debug.xcconfig` or include the `Pods/Target Support Files/Pods-TestClient/Pods-TestClient.debug.xcconfig` in your build configuration.
```

This is confusing, especially for people not familiar with CocoaPods.

This adds a naive check for the CocoaPods-generated xcconfig being #included into the target's actual xcconfig. It also adds the ability to have a special token (I chose `// @COCOAPODS_SILENCE_WARNINGS@ //`, but am happy to change it) in the target's xcconfig to signal that the warning should be silenced even though CocoaPods's xcconfig does not appear to be included. This is useful for test targets and cases where the naive check is not sufficient.

Before rebuilding tarballs or wiping changes by overwriting them by unpacking the files. This also ensures indirectly over the dependency from the spec tasks, that there will be never pending changes in the inner repo.

Don't break the spec everytime when comitting in the inner repo. That should ensure that we can keep the staging area in there clean.

[Linter] Allow to fail-fast

Merge stable-0.36 into master

Add Pod download caching

This way, we never exceed file length limits