@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: 

- [x] Needs tests.
- [x] I don't like the `ReactiveMoyaProvider` extension instance method referencing `ArtsyProvider`, an instance of that class. 

![](http://i.imgur.com/UT69wID.gif)
I agree – unfortunately this is a requirement of Moya: https://github.com/AshFurrow/Moya/blob/e46c9555e7a6acbc42502c8760f5bec860e73d3c/Moya.swift#L108

If we returned stubbed responses immediately on a `RACSignal`, then subscribers to that signal wouldn't have a chance to subscribe before it is completed.