clj-http 1.0.1 upgrade

Brings apodini up-to-date with upstream clj-http. 

The upstream changes in clj-http ended up resulting in an incompatibility because apodini was assuming all headers would be lowercased (which they were prior to clj-http 0.9.2), and also it was merging header maps in a way that they would lose their clj-http HeaderMap magic.

I also figured out that we were being a little aggressive with our auth: with-swift-session was invoking authenticate once for each of the rebound api functions, rather than just once for the whole with-swift-session. The fix for that was pretty simple.

And some other test fixes and whatnots.

Tests pass for me, and I've tried things against a swift cluster I set up using https://github.com/swiftstack/vagrant-swift-all-in-one, and I've patched this into some production use as well.