[WIP] @orta => Basics of transparent self-app-token-fetching API client

There is a call to `.FeaturedWorks` ("/api/v1/sets") in the app delegate as a proof-of-concept. 

The basics of use are, instead of calling `ArtsyProvider.request(.Whatever)` as you normally would, you just call `ArtsyProvider.XAppRequest(.Whatever)`. It'll check if the [XApp token](https://developers.artsy.net/docs/authentication) is present and hasn't expired yet, transparently fetching a new one if required, and signing all non-XApp token requests with the XApp token. 

Work-in-progress because I still want to address: 

- [ ] Needs tests.
- [ ] I don't like the `ReactiveMoyaProvider` extension instance method referencing `ArtsyProvider`, an instance of that class. 

![](http://i.imgur.com/UT69wID.gif)
Right, that's cool. I don't know how the CocoaPods-Keys plugin works exactly, but my understanding was that if someone didn't enter in values for the keys, then either the `EidolonKeys` class wouldn't be created, or it would but it wouldn't have either of the key properties. 

In Objective-C, we'd solve this with conditional `#include`s and `respondsToSelector:`. Just wanted to put it on our radar that those techniques might not wouldn't work with Swift.