Both v1 and v2 of the AWS Ruby SDK accept the string literal AES256, no need to differentiate. (thank you, @trevorrowe)

According to the ImageMagick documentation the '@' flag is a special case that
can be used in conjunction with '>' to prevent IM from scaling an image up.
The '<' flag is ignored when using '@'.

http://www.imagemagick.org/Usage/resize/#pixel

This fixes the issue I reported in #1851

* update aruba methods for in_current_dir and check_file_presence
* switch rspec syntax from should to expect
* configure raise_in_transactional_callbacks if AR >= 4.2
* remove paperclip itself from Appraisal
This also updates Travis to use the default bundler (to enable caching) and to build primary rubies first

It should never be the case that `url` returns `nil`. If there is no url
that can be reasonable achieved, as is the case when the record the
attachment is attached to is unpersisted, then `url` should return the
default url.

For some reason the test in this PR would make all other ones blow up.
For reasons not fully understood at the time of writing, the alternate
spec I'd written doesn't. So, we'll replace that test with this one and
it'll be green.

Thanks to MORI Shingo of DeNA Co., Ltd. for reporting this.

There is an issue where if an HTML file is uploaded with a .html
extension, but the content type is listed as being `image/jpeg`, this
will bypass a validation checking for images. But it will also pass the
spoof check, because a file named .html and containing actual HTML
passes the spoof check.

This change makes it so that we also check the supplied content type. So
even if the file contains HTML and ends with .html, it doesn't match the
content type of `image/jpeg` and so it fails.

consistent with public URLs, this also changes the default behavior
for expiring URLs to use the https scheme rather than http.

Deprecation Warnings:

```
`failure_message_for_should` is deprecated. Use `failure_message` instead. Called from /Users/mugi/git/paperclip/spec/support/matchers/have_column.rb:11:in `block in <top (required)>'.
```

Prioritize MimeMagic over the `file` binary for content type detection
when it finds a match. Fall back to `file` if MimeMagic can't match
anything.

`file` incorrectly detects Open Office XML files (e.g., xlsx, docx) as
zip since they're implemented as zipped archives of xml files. MimeMagic
detects them properly.

* Uses Paperclip's Tempfile instead of Ruby's in Thumbnail
* Also includes a test for TempfileFactory to be sure it does not revert to similar behavior
* In the tests, give the OS some wiggle room in the Tempfile name to ensure the error does not occur before we are ready for it. The wiggle room is needed because the randomized part of the name has a variable number of characters.

Rescue only `NotIdentifiedByImageMagickError` in
`Attachment#post_process_style`. Other errors should bubble up, because
they are meaningless for the end-user, but important for the programmer.

Fixes #1352.

The reason behind this I'm trying to use StringioAdapter inside the mailer, and it fails because `length` used in one of the `mail` gem:
https://github.com/mikel/mail/blob/master/lib/mail/message.rb#L1997

Also you can see that normally `size` has `length` alias, for example in a `StringIO` class:
http://ruby-doc.org/stdlib-1.9.3/libdoc/stringio/rdoc/StringIO.html#method-i-length

Let me know, if this change requires test case, I will add it.

As referenced in #1739

Just because the `Rails` constant is defined, it doesn't mean we're
actually in a Rails app. Since there are people who use Paperclip
outside of Rails, and there's no reason we shouldn't be able to run in
those situations. This commit checks for `Rails.env` instead of just
checking for `Rails` and assuming `Rails.env` works.

This reverts commit 06802254.

Cocaine changes how it returns the supplied path in 0.5.5. While this
has no effect on the workings of Paperclip in a normal capacity, it does
break the tests. This change fixes that and updates the cocaine
dependency to 0.5.5.

Turns out that between fog 1.22.0 and fog 1.25.0, there was a change to
how fog builds S3 expiring URLs. This changes to test to be the common
point between the two versions. All we need to do here is make sure that
the expiring URL is being constructed.

In the process, this also updates all the appraisal-generated
Gemfiles.

Also, in the process, this meant I had to take away the builder version
restriction. This was put in so that `bundle`ing wouldn't take forever,
but I'm unsire whether this needed to happen with this version or if
builder just needed to be separate from the Gemfile. I'm commimtting
this and asking the people who reported the problem. If you don't see a
revet commit, everything was fine.

This reverts commit ae3ec237.