Big 'ol bunch of refactors

A number of different things happened on this branch:

1) API responses got a facelift - new set of supporting classes, main `ApiResponse` class from which to inherit
2) Reimplementation of spot, saved search (anon and auth'd), and employee types responses + clients using new stuffs
3) rspec-pride was added as the default spec run formatter :rainbow:
4) removed a couple dependencies from the Gemfile to gemspec
5) Got rid of all of the names and email address in the Gemfile
6) Bumped .ruby-version hint file to latest ruby 1.9.3 for update against [CVE-2013-4164](https://www.ruby-lang.org/en/news/2013/11/22/heap-overflow-in-floating-point-parsing-cve-2013-4164/)
7) Tests for all the things - coverage is now just barely over 97%
8) added gem rb-readline for linux development support 
9) version bump to 2.0.0 to reflect breaking change in public interface. From the endpoint clients, we will no longer return arrays with magic methods tacked on. Now there are clearly defined methods for errors, timing, and models on the returned subclass of ApiResponse, and none of them work by using metaprogrammed sorcery.

Verification steps:
Since there are a lot of commits here as well as a number of different things going on, here's how it might be easiest:
- The main meat of the logical refactoring is the stuff around API responses/metadata. In lib/cb/responses, take a look at api_response.rb, metadata.rb, errors.rb, and timing.rb. These are the classes that make up the new API response design. 
- I went ahead and reimplemented the spot, saved search, and employee types clients + responses, check those out and see how the new design feels/smells.
- Are we cool with rspec-pride formatting our spec output? 
- Are the changes to the gemspec ok? (teams instead of names, ConsumerDevelopment@cb is the contact email now)

:bear::rocket: