not escape to timestamp

@see https://github.com/thoughtbot/paperclip/commit/804b4edc1d8d7ca9865170e34f26da7d66f6d0d5#commitcomment-8497017
Fixup formatting of "not escape to timestamp"
Fast to slowly spec

```
 paperclip $ rspec spec/paperclip/integration_spec.rb --profile 1
Testing against version 4.1.7
.........................[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
.........

Finished in 15.19 seconds (files took 0.60155 seconds to load)
34 examples, 0 failures

Top 1 slowest examples (9.54 seconds, 62.8% of total time):
  Paperclip Many models at once does not exceed the open file limit
    9.54 seconds ./spec/paperclip/integration_spec.rb:18
```

to

```
 paperclip $ rspec spec/paperclip/integration_spec.rb --profile 1
Testing against version 4.1.7
.........................[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
.........

Finished in 10.95 seconds (files took 0.59585 seconds to load)
34 examples, 0 failures

Top 1 slowest examples (5.33 seconds, 48.7% of total time):
  Paperclip Many models at once does not exceed the open file limit
    5.33 seconds ./spec/paperclip/integration_spec.rb:18
```

at trim indent
remove whitespace, not main gemspec
Fog upgraded how expiring_urls are made

During the fixing of the previous commit, the tests broken. 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.
Revert "Fog upgraded how expiring_urls are made"

This reverts commit 8e0eb4ce3aeb9bf73222474e9693a07edfda08a7.
Revert "remove whitespace, not main gemspec"

This reverts commit 8d70c1984a0df087066380e14a1650fcb799b9c1.
Revert "Fast to slowly spec"

This reverts commit ae3ec2373be510d4f6555f923d56829bfd9e5f04.
Fog upgraded how expiring_urls are made

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.