reset_column_infomation shouldn't be part of the assertion.
use self instead of #read_attribute
Allow polymorphic routes with nil when a route can still be drawn

Suppose you have two resources routed in the following manner:

```ruby
resources :blogs do
  resources :posts
end

resources :posts
```

When using polymorphic resource routing like `url_for([@blog, @post])`, and `@blog` is `nil` Rails should still try to match the route to the top-level posts resource.

Fixes #16754
Since /console is an optional feature, mention <%= console %> instead.

(/console is not mounted by default with web-console 2.0.)
Merge pull request #16747 from rsutphin/web-console-gemfile-comment

Clarify that /console is an optional feature
Keep it closer to the original wording [ci skip]
Merge pull request #16755 from codeodor/master

Allow polymorphic routes with nil when a route can still be drawn
Clear schema cache before each test
Fix for configuring rails guide

`ActiveSupport::Logger` has no concept like auto flushing since it has no userspace buffering.
It's a remnant of `ActiveSupport::BufferedLogger` epoch which was since removed from rails.
Merge pull request #16763 from brainopia/patch-1

Fix for configuring rails guide [ci skip]
Clear schema cache before each test
Merge pull request #16704 from ankit1910/use-existing-method

use self instead of #read_attribute
Use `safe_constantize`.

Fixes https://github.com/rails/rails/issues/9933.
Use jquery-rails master
Try with web-console master
Remove warning
Break conditional branches into separate methods

This breaks the two branches of the `if reflection.last` and `else`
to clearer see where the two methods can be refactored. Eventually
we hope to remove the need for these separated methods altogether.

Move the first branch outside the loop

This code doesn't need to be in the loop because it it always affects
the last chain. `get_bind_values` and `add_constraints` must match
in this context because `get_bind_values` is the caching of `add_constraints`

Use each_cons to remove need for `chain[i + 1]`

The `chain[i + 1]` is confusing because it's not immediately obvious
what it's trying to achieve. The use of `each_cons` makes it clear
we need to get the `next_reflection`.
Add test to assert the right sanitizer vendor is being used
Move implementation to the gems

Now we keep only the common code and move the specific code to the gems
MySQL: skip GTID-unsafe statement tests when enforce_gtid_consistency is enabled