Minor grammar fixes for Rails 5.1 release notes

[ci skip]

[ci skip]

[ci skip]

[ci skip]

Fixing tons of grammar, etc.

[ci skip]

Move new CHANGELOG entry to the top [ci skip]

Improve Caching with Rails Guides [ci skip]

Track the version-compatible config settings inside railties

Action View overrides `url_for` in the view context to render paths by
default when using `url_for` and this means that direct route helpers
don't get the full url when called with the url suffix. To fix this
always call the original `url_for`.

Instead of forcing new applications to carry an initializer that just
switches things to what their default "should" be, we can handle it
internally.

The initializer is then only used by upgraders: it shows what the new
default would be (commented out), while their upgraded application
continues to operate as it did before.

Under this model, a multiply-upgraded application could accumulate
several new_framework_defaults_*.rb files, for each release series it
has traversed. A given release series only needs to generate the latest,
though, because we don't support `rails app:upgrade` while skipping
releases.

Adds the "Caching in Development" section to
demonstrate usage of the dev:cache task in development mode.

Also, makes a small grammatical correction in section 2.4.

Allow order to be given expressions as hash keys

Drop comments from structure.sql in postgresql

[ci skip]

Add first draft of release notes for Rails 5.1 🎉

This was causing an infinity loop since it was delegating to `all` and
all delegating back to this module.

Not all requirements can be expressed in terms of polymorphic url
options so add a `route_for` method that allows calling another
direct route (or regular named route) which a set of arguments, e.g:

    resources :buckets

    direct :recordable do |recording|
      route_for(:bucket, recording.bucket)
    end

    direct :threadable do |threadable|
      route_for(:recordable, threadable.parent)
    end

This maintains the context of the original caller, e.g.

    threadable_path(threadable) # => /buckets/1
    threadable_url(threadable)  # => http://example.com/buckets/1

Pass options to `driven_by`

Remove ability update locking_column value

Use it to specify that an association should be initialized with a
particular record before validation. For example:

    # Before
    belongs_to :account
    before_validation -> { self.account ||= Current.account }

    # After
    belongs_to :account, default: -> { Current.account }

Capybara was updated in teamcapybara/capybara#1841 to use Minitest style
assertions so that system test output shows x number of assertions, x
numbe of failures, etc.

Before:

```
6 runs, 0 assertions, 0 failures, 0 errors, 0 skips
```

After:

```
6 runs, 7 assertions, 1 failures, 0 errors, 0 skips
```

This change bumps Capybara from 2.7.0 to 2.13.0 and includes the
required minitest assertion file in the test case. 🎉

Fix guide incorrectly refers to public/assets/images [ci ckip]

Updates incorrect documentation [ci skip]

Add documentation to use with_options anywhere in the same class [ci

Looking on code for this method it's clear that it's just returns `response.status` instead of full `response` object.
It's better to correct docs as probably lots of specs are relying on this behavior.

We are overriding it in `Time` and `ActiveSupport::TimeWithZone` so
there's no point in having it in the `DateAndTime::Compatibility`
module. Also add some docs for the `to_time` implementations.

Allow Time#to_time on frozen objects. Return frozen time rather than "RuntimeError: can't modify frozen Time"

Add secrets edit test

PR was merged before I could finished reviewing 😬

[ci skip]

In 9b654d47 some params munging was added to ensure that they were
set whenever `recognize_path` would call either a proc or callable
constraint. Since we no longer mutate the environment hash within
the method it's now unnecessary and actually causes params to leak
between route matches before checking constraints.

Fixes #28398.

Fix fragile test (`AssociationProxyTest#test_save_on_parent_saves_children`)