bring back `db:test:prepare`.

The records weren't being replaced since equality in Active Record is
defined in terms of `id` only. It is reasonable to expect that the
references would be replaced in memory, even if no queries are actually
executed. This change did not appear to affect any other parts of the
code base. I chose not to execute callbacks since we're not actually
modifying the association in a way that will be persisted.

Fixes #17730

This reverts deprecations added in #13528.
The task is brought back for two reasons:
  1. Give plugins a way to hook into the test database initialization process
  2. Give the user a way to force a test database synchronization

While `test:prepare` is still a dependency of every test task, `db:test:prepare`
no longer hooks into it. This means that `test:prepare` runs before the schema
is synchronized. Plugins, which insert data can now hook into `db:test:prepare`.

The automatic schema maintenance can't detect when a migration is rolled-back,
modified and reapplied. In this case the user has to fall back to `db:test:prepare`
to force the synchronization to happen.

[Rafael Mendonça França & Yves Senn]

This require caused the `active_record.set_configs` initializer to
run immediately, before `config/initializers`. This means that setting any
configuration on `Rails.application.config.active_record` inside of
an initializer had no effects when rails was loaded through `rake`.

Introduced by #6518

/cc @rafaelfranca

Fixing wrong link in 'Ruby on Rails 3.0 Release Notes' [ci skip]

Combine aliased_table_for and aliased_name_for

Don't center the routes table on routing errors

The tests to verify our testing setup used `RAILS_ENV=development`
to execute the tests. Let's keep it as close to a real-world setup
as possible.

Closes #17615 #17616

when script_name is nil in the options hash, script_name is set to nil.

options = {script_name: nil}
script_name = options.delete(:script_name) {‘’} # => nil
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Closes #17756

[Godfrey Chan, Zachary Scott]

This removes the unwanted deprecation warnings in the tests

This is a follow-up to 116de073. That change was for two reasons: 1) speed up the
tests by reducing the amount of log lines 2) avoid a deprecation warning from
a6de6f50.

This setting need to be on the basic app too, otherwise the deprecation warning
will show up on other unrelated test cases.

Fix out of range error message

Always default the log_level to :info for Railties

Add a CHANGELOG entry for #16622 and a6de6f50 [ci skip]

Add release note for #17743 [ci skip]

Refs #17684: Enhances rdoc for ActiveJob assert_performed assertions

It will set proper queue_adapter state required by assert_performed_jobs assertions.

Also the block version of assert_performed_jobs will make sure this
state is respected.

Fixes #17684