In a previous patch, all log-related stuff was removed. However,
some logs are still useful to understand the code. Therefore, in
this patch, I put those log messages back as comments.

[ci skip]

If the code reaches that line new_constants is no longer needed.
We only need here to iterate over it to discard stuff and done.

Note that constant_watch_stack.new_constants returns a new
reference each time it is invoked, so that #clear call was not
cleaning state in some internal structure (which would have been
a bit dirty as well at this level of coupling).

This array literal cannot be reached. The previous begin either
returns to the caller via the explicit return in the ensure
block if all goes well, or else propagates whatever make the
begin block abort execution.

I have investigated the origin of this a bit. In the past the
ensure block didn't have a return call, see for example c08547d2.
Later on the return was added in 4da45060, but the trailing
literal was left there.

References #24205.

Lets have the server and the Rake task go through the same ropes, so we can
share all the file lookup, adding, and deleting code.

Update action_controller_overview.md

Remove log-related stuff from ActiveSupport::Dependencies

In this patch, all log-related stuff in `ActiveSupport::Dependencies`
is removed because the logging is no longer useful.

Correct command for generating secret_key_base [ci skip]

[ci skip] Fix the FinderMethods#find document

We should use #find_or_initialize_by and #find_or_create_by because #first_or_initialize and #first_or_create methods are not the public API

add `queue_classic` to list of provide `provider_job_id` [ci skip]

add headers to payload list [ci skip]

Follow up to #24115.

silence deprecation message for dynamic controller and actions on Action View test

Follow up to #23980.

Add explanation about accepts_nested_attributes_for keys in the strong parameters docs

Fix `warning: method redefined; discarding old female`

Add explanation about accepts_nested_attributes_for keys in the strong parameters documentation [skip ci]

```
$ ARCONN=mysql2 be ruby -w -Itest test/cases/scoping/default_scoping_test.rb
Using mysql2
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: method redefined; discarding old female
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: previous definition of female was here
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: method redefined; discarding old male
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: previous definition of male was here
```

Fix Gemfile.lock

- Resque version was locked to < 1.26 in 92f869a0 but
  Gemfile.lock was not updated.

regenerate application_mailer.rb if it is missing

The BINARY Operator is only needed for string columns

Right now referencing the constant `AbstractController::Rendering`
causes `ActionView::Base` to be loaded, and thus the load hooks for
action_view are run. If that load hook references any part of action
view that then references action controller (such as
`ActionView::TestCase`), the constant `AbstractController::Rendering`
will attempt to be autoloaded and blow up.

With this change, `ActionView::LoadPaths` no longer requires
`ActionView::Base` (which it had no reason to require). There was a
needed class from `AbstractController::Base` in the Rendering module,
which I've moved into its own file so we don't need to load
all of `AbstractController::Base` there.

This commit fixes
https://github.com/rails/rails-controller-testing/issues/21

Clarify has_many :dependent option docs [ci skip]

Clarifies the documentation here to mean all options are for when the
relation is destroyed; also now reflects the documentation on this same
option found in the has_one section.

There was some subtle breakage caused by #18774, when we removed
`#original_exception` in favor of `#cause`. However, `#cause` is
automatically set by Ruby when raising an exception from a rescue block.
With this change, we will use whichever handler has the highest priority
(whichever call to `rescue_from` came last). In cases where the outer
has lower precidence than the cause, but the outer is what should be
handled, cause will need to be explicitly unset.

Fixes #23925

I'm unsure how this passed CI in the pull request.