Fix issues with running Ruby 2.0.0 and using Heroku Toolbelt

The issue was that bundle sets ENV['RUBYOPT'] after it has been
loaded, which causes any subprocesses that get spawned
to be confused. If you spawn the processes using the incantation
"Bundler.with_clean_env", the RUBYOPT will be temporarily restored.

See for more info:
http://pivotallabs.com/service-oriented-foreman/

We wrote a cucumber test (shell_execution.feature) that exposes
the problem, but it requires that you have the Heroku Toolbelt
installed (not the gem) as well as RVM and Ruby 2.0.
Merge pull request #155 from tjgrathwell/fix-for-ruby-2

Fix issues with running Ruby 2.0.0 and using Heroku Toolbelt
Allow integration tests to run on Travis

- Use addons that do not require verification
- Add cucumber and travis tasks
Update dependencies for Travis
More Travis updates

- Upgrade RSpec
- Configure git user
Restrict testing to Rails 3.2
More Travis updates

- Disable strict host checking
- Check the environment
- Lock down rails to 3.2.7
- Add pg
Travis updates

- parameterize ruby version in Gemfile creation
- create and add deploy key
Add blank password setting to ssh-keygen
s/install/before_install/
Clean up keys after builds
TRAVIS_BUILD_ID is not unique enough. Use JOB_NUMBER instead
s/TRAVIS_JOB_NUMBER/TRAVIS_JOB_ID/
Version bump to v4.3.1
Remove extraneous addon from tests

- Heroku was erroring out (unavailable), but it is YAGNI
Update openssl in Travis

- Fixes intermittent failure when bundler connects to rubygems.org
Defer evaluation of the Heroku auth token

- HerokuSan::API was trying to evaluate the auth token at construction time, instead of waiting until it was actually needed, if ever.
- Fixes #156
Version bump to v4.3.2
Add Gemnasium badge
The Future is GitHub releases