(QENG-104) Remove gems that were pinned for Ruby 1.8

We no longer use ruby 1.8 internally. There is no reason to keep it
around any longer.

![nuke the entire site from orbit](http://iruntheinternet.com/lulzdump/images/gifs/alien-sigourneyweaver-nuke-riley-orbit-1348491814r.gif)
What happens for... say the Apache module, which still run unit tests on Ruby 1.8. So then it will still run `bundle install` on Ruby 1.8, will this break `bundle install` on Ruby 1.8... Wouldn't it be better to just list Ruby 1.8 as unsupported in the README, maybe send an email out to users letting them know that we're going to drop Ruby 1.8 support (and if they need to keep `bundle install` working then they'll need to do X things). Then do a full clean up of the gemfile?