Short circuit on unmatched etag.

In my situation, I'd already completed Heroku deployments which left the asset
in S3 with a modified time greater than my local copy. The etag and md5
comparisons were being evaluated properly, but the last modified time was still
the descision-maker for deleting the file. But...the contents are different, so
we definitely need to update the remote copy.