[ci skip] Modify twitter api link in api guide

* The twitter developer site's url was changed.

Use current_config in structure_dump

Deprecate controller level force_ssl

Today there are two common ways for Rails developers to force their
applications to communicate over HTTPS:

* `config.force_ssl` is a setting in environment configurations that
  enables the `ActionDispatch::SSL` middleware. With this middleware
  enabled, all HTTP communication to your application will be redirected
  to HTTPS. The middleware also takes care of other best practices by
  setting HSTS headers, upgrading all cookies to secure only, etc.
* The `force_ssl` controller method redirects HTTP requests to certain
  controllers to HTTPS.

As a consultant, I've seen many applications with misconfigured HTTPS
setups due to developers adding `force_ssl` to `ApplicationController`
and not enabling `config.force_ssl`. With this configuration, many
application requests can be served over HTTP such as assets, requests
that hit mounted engines, etc. In addition, because cookies are not
upgraded to secure only in this configuration and HSTS headers are not
set, it's possible for cookies that are meant to be secure to be sent
over HTTP.

The confusion between these two methods of forcing HTTPS is compounded
by the fact that they share an identical name. This makes finding
documentation on the "right" method confusing.

HTTPS throughout is quickly becomming table stakes for all web sites.
Sites are expected to operate over HTTPS for all communication,
sensitive or otherwise. Let's encourage use of the broader-reaching
`ActionDispatch::SSL` middleware and elminate this source of user
confusion. If, for some reason, applications need to expose certain
endpoints over HTTP they can do so by properly configuring
`config.ssl_options`.

Remove expired explanation [ci skip]

Override callback doesn't work anymore.

Adding missing extension for `cattr_accessor` method

https://travis-ci.org/rails/rails/jobs/360109429

Don't unset foreign key when preloading missing record

Previously `relation.all` behaves as `relation.scoping { klass.all }`.
But it is just enough to `relation.spawn`.

This looks like a typo from 0f0aa6a2

--frozen-lockfile is the right name of the argument

Use `did_you_mean` spell checker for option suggestions

[Webpack] Raise an error when lockfile diff is generated

Compare ruby version with correct way

Fix deprecation warnings from with_lock

Expose foreign key name ignore pattern in configuration

 Flip the order of the after_create callbacks

Addresses rails/rails#32247

Add test that checks identify and analyze work in correct order

Break out direct upload test helper

Review changes for direct-upload test helper

Add `before?` and `after?` methods to date and time classes

Part 1 Easy Multi db in Rails: Add basic rake tasks for multi db setup

Readability fix [ci skip]

Not everything that responds to `routes` is a Rails engine - for example
a Grape API endpoint will have a `routes` method but can't be used with
`assert_recognizes` as it doesn't respond to `recognize_path_with_request`.

Fixes #32312.

When a belongs to association's target is set, its foreign key is now
updated to match the new target. This is the correct behaviour when a
new record is assigned, but not when the existing record is preloaded.

As long as we mark the association as loaded, we can skip setting the
target when the record is missing and avoid clobbering the foreign key.

Add custom prefix to ActiveRecord::Store accessors

Now that we require Ruby over `2.3`, we can replace the current
suggestion methods we have with tooling from the `did_you_mean` gem.

There is a small user visible change and this is that we now offer a
single suggestion for misspelled options. We are suggesting fixes during
generator invocation and during a mistyped rails server rack handler. In
both cases, if we don't make a proper prediction on the first match, we
won't do so in the second or third one, so in my mind, this is okay.

The multiple assignments was caused by 37a1dfad due to lost the `to_s`
normalization for given names.

Fixes #32323.

Add a prefix option to ActiveRecord::Store.store_accessor and
ActiveRecord::Store.store. This option allows stores to have identical keys
with different accessors.

Fix Cache `read_multi` with local_cache bug, should returns raw value, not `ActiveSupport::Cache::Entry` instance.

Use ASCII-8BIT paths in ActionDispatch::Static