ensure s3 objects are coming out of Virginia

From @mfine:

S3 objects are sitting in the wrong side of the country, eventual
consistency be damned. There is no US East region in S3; there is
something called US Standard, and it runs out of Virginia AND Seattle
datacenters. It's a legacy artifact and a source of endless operational
pain within AWS. Objects are intended to be replicated across the
datacenters, but sometimes this doesn't work out, and objects get stuck
in one datacenter or the other. Since we run everything out of US East,
it's operationally prohibitive to get things stuck in Seattle. This is a
per object issue, not a per bucket issue - objects in the same bucket
can end up in either Virginia or Seattle.

This is really easy to do by accident - upload an object from your
laptop in San Francisco, and you get bound to the Seattle datacenter.
AWS provides endpoints that will bind objects either to Virginia or
Seattle in US Standard. Be safe and prefer using
s3-external-1.amazonaws.com.

You can read more about it here:
https://forums.aws.amazon.com/message.jspa?messageID=185820
Merge pull request #151 from hone/s3_virginia

ensure s3 objects are coming out of Virginia
refactorings from @tenderlove
if using bundle exec, -rbundler/setup fudges with RUBYOPT
Remove extra / unmatched double quote
Merge pull request #158 from heroku/remove-extra-quote

Remove extra / unmatched double quote
Setup a default bundler cache for ruby 2.0.0 (default ruby)
use the patchlevel for default cache
if the cdn.yml is empty, return a Hash
try using S3 instead of Cloudfront
update changelog
v81
[close #159] Remove deprecated asset behavior

Rails3 deploys that do not successfully run `assets:precompile` will now fail.
The default cache skips installing nokogiri

Not sure how this wasn't caught earlier but with the default cache, nokogiri doesn't get installed using Ruby 2.0.0. We may want to change how we're testing for this, but for now this spec fix should keep the suite working for now.

Here is the new output:

```
-----> Fetching custom git buildpack... done
-----> Ruby app detected
-----> Using Ruby version: ruby-2.0.0
-----> Installing dependencies using Bundler version 1.3.2
       New app detected loading default bundler cache
       Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin --deployment
       Using mini_portile (0.5.1)
       Using nokogiri (1.6.0)
       Using bundler (1.3.2)
       Your bundle is complete! It was installed into ./vendor/bundle
       Bundle completed (0.53s)
       Cleaning up the bundler cache.
       Removing sass (3.2.10)
       Removing railties (4.0.0)
       Removing rails_serve_static_assets (0.0.1)
       Removing activerecord-deprecated_finders (1.0.3)
       Removing polyglot (0.3.3)
```
Merge pull request #161 from heroku/schneems/remove-runtime-asset-compilation

[close #159] Remove deprecated asset behavior
move benchmark require to top
if buildpack version is 0, should not clear the cache
[close #29] Better Retry/Failure Support for Curl


http://stackoverflow.com/questions/14857407/ruby-trying-to-run-set-command
Do as little work in Detect as possible
v82