Update to latest versions of all gems.

…except multi-json. Something changed about one of
the errors we depend on :(.
Update multi-json.
Update changelog.
Merge pull request #343 from vcr/update-gems

Update gems
Fix file name sanitization.

This better handles file names with dots in the path
and no file extension.

Fixes #344.
Merge pull request #346 from vcr/fix-issue-344

Fix file name sanitization.
Support Unix sockets
Update version of Excon with new feature
Swap method declaration and if statement
Move legacy excon methods into a helper module.

By putting it in a separate file it's not loaded and
counted in the simplecov coverage calculation,
which matters since we're not running our build against
the old version of Excon.
Excon 0.28 works.
Changelog and README update for #345.
Be tolerant of ::Excon::Utils being undefined.

It was added in Excon 0.27.5, and we support
older excon versions than that.
travis: cache bundle across jobs

Installing dependencies via Bundler can make up a large portion of
the build duration. Caching the bundle between builds drastically
reduces the time a build takes to run.

Caching does not become effective until this commit is merged
to master. At that point, `bundle install` on travis takes
20-30 seconds instead of several minutes. If a branch modifies
the gemspec, then that branch starts with the cache but still
uses the updated gemspec.

In my experience with travis-ci bundler cache, only the default
branch *writes* the cache. All other branches merely *read*.

http://about.travis-ci.org/docs/user/caching/
Merge pull request #349 from jumanjiman/cache

travis: cache bundle across jobs
Merge pull request #347 from vcr/improve-on-345

Improve on 345
Revert "travis: cache bundle across jobs"

This reverts commit c5e90d06ad8adb0cc066a04cb22fe22c3cc2935c.

Merging that commit caused the build to start failing due to the fact
that it changed where the bundled gems are installed, and our
warnings prevention assumes a warning originated from VCR (and thus is
worthy of failing the build) if it includes a filename that is in the
current working directory.  Previously the bundled gems were
installed outside of the working directory and thus warnings from
dependent gems (like WebMock) would not trigger a failure.

We should re-work the warnings prevention logic, but for now
I'm reverting this to get back to green.
Fix Faraday middleware so it doesn't halt the request.

…when another adapter is exclusively enabled.
Reword the "version too high" warning message.
Merge pull request #352 from vcr/a-couple-fixes

A couple fixes