This refactor incidentally fixes a corner case when `translate` is
called with a block, the translation is missing, and
`debug_missing_translation` is false.

This commit adds a test for the above corner case, and additional tests
for existing behavior.

Rename Error#detail method as details

Plural is more expected.

Update Minitest to allow installation with Ruby 3.

https://github.com/seattlerb/minitest/commit/9713c5536287a028e3eeab04521b3dc22dc61724

Prior to this commit, when a translation key indicated that the
translation text was HTML, the value returned by `I18n.translate` would
always be marked as `html_safe`.  However, the value returned by
`I18n.translate` could be an untrusted value directly from
`options[:default]`.

This commit ensures values directly from `options[:default]` are not
marked as `html_safe`.

Prior to this commit, when a translation key indicated that the
translation text was HTML, the value returned by `I18n.translate` would
always be marked as `html_safe`.  However, the value returned by
`I18n.translate` could be an untrusted value directly from
`options[:default]`.

This commit ensures values directly from `options[:default]` are not
marked as `html_safe`.

Prior to this commit, when a translation key indicated that the
translation text was HTML, the value returned by `I18n.translate` would
always be marked as `html_safe`.  However, the value returned by
`I18n.translate` could be an untrusted value directly from
`options[:default]`.

This commit ensures values directly from `options[:default]` are not
marked as `html_safe`.

It is a common use case especially for MySQL users.

Revert #40178

Use a unique controller class per ActionView::TestCase

This reverts commit b8ab1f89, reversing
changes made to 73ae5655.

Properly support `reverse_order` on relations with `nulls_first` or `nulls_last` calls

If you're using the `nulls_first` or `nulls_last` functionality with an explicit ordering, then previously it wasn't properly handling calls to `#reverse` (called through `reverse_order`). This commit changes the behavior to match what would be expected.

It's faster on Ruby 2.7+ since it avoids rehashing the keys.

These methods are PostgreSQL-specific, and all supported versions of
PostgreSQL support validating constraints.

Add support for `NOT VALID` check constraints in PostgreSQL

Active Record already supports adding `NOT VALID` foreign key constraints in PostgreSQL, but back in #31323 when check constraint support was initially added, the ability to add a check constraint and validate it separately was not included. This adds that functionality!

Anchor BacktraceCleaner gem filter regexp

This ensures the default gem filter does not affect backtrace lines that
have a subpath incidentally matching a gem path.

Fixes #40196.

Closes #40187.

Update Gemfile.lock with rubocop-packaging

Load Rails tasks for each new Rake::Application

Follow-up to #40185.

Follow-up to #40143.

Rails Rake tasks are loaded for each new `Rake::Application` instance
via `Rails.application.load_tasks`.  However, under the hood,
`Rails.application.load_tasks` used `require` instead of `load`, which
caused Rails tasks to be loaded for only the first `Rake::Application`
instance.

This commit changes the relevant `require` to `load`.

Fixes #40184.

Update RuboCop to v0.90

Signed-off-by: NUtkarsh Gupta <utkarsh@debian.org>

Add explain to abstract database statements.

Support reversing of Arel expressions in reverse_order, last etc.

Shorten inspect on ActionDispatch::Request

Shorten inspect on AbstractController::Base

Calling self in an action of a controller generates an endless stream of
characters, including the request object and all instances variables.
This can be frustrating when using a debugger in a controller and
accidentally calling `self` generates output for a couple of seconds.

This shortens inspect to only show the class name.

    MyController.new.inspect # => "#<MyController:0x00000000005028>"

Calling request in an action of a controller generates an endless stream of
characters, including the Rack app and middlewares.
This can be frustrating when using a debugger in a controller and
accidentally calling `request` generates output for a couple of seconds.

Inspect on ActionDispatch::Request is shortened to the most relevant
attributes and uses the same format as used for request in the logs:

    "#<ActionDispatch::Request POST "https://example.com/path/of/some/uri?q=1" for 1.2.3.4>"

Reduce allocations in expanded_version and expanded_key

Disconnect connections used for acquiring advisory lock in migration.

Raise error when `from` is used with `delete_all`.

Avoid setting `ActiveRecord::Base.configurations` twice in db rake ta…

This prevents the `from` query method from being ignored silently in the
resulting SQL query that is generated.

The current behaviour of reverse_order, when presented with an
existing order that is an Arel expression, is to ignore it.
This isn't quite in keeping with how it handles Arel attributes
(which it reverse) or arbitrary strings (which throw an exception).

The easy path would be to throw an exception, but we don't have to.
Any SQL expression that is a valid default sort expression can be
reversed with DESC.

It follows that if there's an existing Arel::Nodes::NodeExpression
that is not already wrapped with an Arel::Nodes::Ordering, then
it can be reversed with DESC.