Separating Http interface from RiakJson library logic

### High Level
RiakJson is now simply a library of modules whose core responsibilities are:

##### Riak K/V Integration
* CRUD Operations given a "Collection", "Key", and "Document" using Riak K/V

##### Riak Search Query Integration
* Translation of Json queries to Solr queries
* Execution of those queries on Riak Search
* Building a Json result set from the Solr query results

##### Riak Search Schema Integration
* Translation of Json schemas to Solr XML schemas and back
* CRUD Operations given a "Collection", "SchemaName", and "Schema" using Riak Search
* BucketType and Index management / abstraction for searchable "Collections" / buckets

### Future refactor plans
* The translation modules could be separated from the parts that actually integrate with Riak K/V and Search so that they can be used by any erlang client application outside of Riak