Clear Resolvers' cache after RenderTestCases tests

Allow column name with function (e.g. `length(title)`) as safe SQL string

`split(/\s*,\s*/)` to order args and then `permit.match?` one by one is
much slower than `permit.match?` once.

Add forgotten nodoc to dump_schema method.

Allow quoted identifier string as safe SQL string

Fix preloading on AR::Relation where records are duplicated by a join

Include warning in docs about polymorphism in underlying tables

fix typo in CHANGELOGs.

Move schema cache to pool

Fixed db:prepare task for multiple databases.

Treat ActiveRecord::Base and ApplicationRecord as "primary"

Extract default log file open operation to method

Fix sqlite3 collation parsing when using decimal columns.

Don't call listen with empty directory list

Fix EventedFileUpdateChecker through a symlink 

Do not clear deprecated initializer dependencies if using classic autoloader

`Rails::Application::Finisher` defines a `:let_zeitwerk_take_over` initializer. This initializer is always run but it's statements are wrapped in a guard: `config.autoloader == :zeitwerk`.

`Finisher` also defines a `initializer :warn_if_autoloaded` initializer with a `before: :let_zeitwerk_take_over` option which also always runs. This initializer unloads any constants autoloaded during initialization and displays a deprecation warning. This initializer does not account for `config.autoloader` being set to `:classic`.

The problem is that this initializer changes the behavior of the classic autoloader. Constant autoloading from initializers is deprecated but the deprecation should not break existing applications which currently depend on autoloaded constants in initializers.

This commit prevents the dependencies from being unloaded if the autoloader is not Zeitwerk. It also updates the deprecation warning, if the classic autoloader is enabled, to indicate that the constants would have been unloaded if Zeitwerk had been used.

Only clear cache when view paths are specified

Fix invalid schema dump when primary key column has a comment

Avoid making extra 5 arrays in each `save`

Fix table comment also being applied to the primary key column

Change `ActionDispatch::Response#content_type` returning Content-Type header as it is

Fail parallel tests if workers exit early

The other template files do not add `frozen_string_literal`, so should
behave the same.

Ref: #30342, #30348.

https://buildkite.com/rails/rails/builds/61362#99165d42-172d-4ad5-bf72-b29d8cd44f3e/995-1006

Use WeakRef in Reaper to avoid leaking connection pools

Use a single thread for all ConnectionPool Reapers

https://buildkite.com/rails/rails/builds/61358#a78ee50e-30b5-48a2-858f-63eba287d919/1290-1298

This reverts commit a1ee4a9f.

Even if a1ee4a9f is applied, CI is still flakiness.

https://buildkite.com/rails/rails/builds/61252#2c090afa-aa84-4a2b-8b81-9f09219222c6/994-1005
https://buildkite.com/rails/rails/builds/61252#2e55bf83-1bde-44a2-a4f1-b5c3f6820fb4/929-938

Failing tests by whether schema cache is filled or not, it actually
means that whether SCHEMA SQLs are executed or not is not target for the
tests.

So I've reverted commit a1ee4a9f which filling schema cache before
`assert_no_queries`, and replace `assert_no_queries` to
`assert_queries(0)`.

Fix unexpected select_tag delete behavior when include_blank is present

Don't round off subseconds unless necessary

Allow symbol (i.e. quoted identifier) as safe SQL string

[documentation][ci skip] stringify_keys and symbolize_keys have stable results.

The initializer receives `nil` for these options when no cofigurations were given:
https://github.com/rails/rails/blob/v6.0.0.rc1/activerecord/lib/active_record/railtie.rb#L91-L97

Change comments

[ci skip]

Wrap ActionView cache expiry in a mutex

 Bump Gemfile entry jbuilder version

Remove compatibility module from docs [ci skip]