(TK-29) Add query params to Java client

Add query params back into the Java client, along with tests
to validate this functionality is working.
(TK-29) Add query params option to clj client

Add query parameter support to the clojure client. User can now
specify a :query-params option in the options map containing a
map of query parameters.
(TK-29) Overwrite parameters set in URL

Overwrite parameters set in the URL of a request if query
parameters are specified in the options map. If no parameters are
set in the options map, any query parameters set in the URL will
NOT be overwritten and will be successfully passed as part of the
request.
Reformat query-options variable

Reformat the query-options variable to line things up and
increase readability.
(TK-29) Use :query-params and change variable names

Use :query-params in the query param ring handler instead of
:params. Also change variable names used for testing.
(TK-29) Move to URI instead of String

Have the RequestOptions constructor take a URI instead of a
string. Add signature to the HTTP request methods that take
a URI.
(TK-29) Address PR comments

Address PR comments by changing CoercedRequestOptions to use
a URI instead of a String, simplifying HTTP method calls, and
removing unused imports.
Update to apache 4.0.2
Merge pull request #11 from cprice404/maint/master/upgrade-to-apache-4.0.2

Update to apache 4.0.2
Update CHANGELOG for 0.2.1 release
lein-release plugin: preparing 0.2.1 release
lein-release plugin: bumped version from 0.2.1 to 0.2.2-SNAPSHOT for next development cycle
Merge pull request #10 from fpringvaldsen/TK-29-add-query-params

(TK-29) Add support for query parameters
Update CHANGELOG for 0.2.2
lein-release plugin: preparing 0.2.2 release
lein-release plugin: bumped version from 0.2.2 to 0.2.3-SNAPSHOT for next development cycle
lein-release plugin: preparing 0.2.3 release
lein-release plugin: bumped version from 0.2.3 to 0.2.4-SNAPSHOT for next development cycle
(PE-5567) Fix bug if content-type header has no charset

Prior to this commit, the Java client API would throw an NPE if
it got a response from a server where the Content-Type header
did not include a charset.
Merge pull request #12 from cprice404/bug/master/PE-5567-npe-if-no-charset

(PE-5567) Fix bug if content-type header has no charset