"Mini Test" was used in #5012 but "minitest" is
the correct product name.
See also: https://github.com/minitest/minitest/blob/master/README.rdoc#description

> minitest provides a complete suite of testing facilities
> supporting TDD, BDD, and benchmarking.

In this description, "minitest" is used.

[ci skip]

Signed-off-by: Carlos Antonio da Silva <carlosantoniodasilva@gmail.com>

…5822)

A previous change #4834 introduced a downcase call to each attribute, so
that it'd fix an invalid grammar issue on some languages like English
that were showing `Email` in the middle of flash message sentences.

However, it caused a bug with German which uses the word `E-Mail` and at
the beginning of the sentence, causing it to be converted to `E-mail`
incorrectly.

The fix here will only downcase the first char of each word, and convert
it back to upcase at the beginning of the sentence, which should work
for both the original fix (English message), and for the new bug (German
 message)

If we end up running into any more of these edge cases with the message,
we might roll it all back and provide a different set of interpolation
values for the original vs downcased translations, so people can use
what makes the most sense for each language without us having to
manually massage these strings.

Fixes #5820

…et" button (#5824)

This mirrors #5515

The config exists at the model/resource class from the registerable
module, but it was not being honored, instead we were directly relying
on the main Devise config.

Now this can be configured and honored per-model/resource class, as
expected.

This is similar to #5429 and `sign_in_after_reset_password` fix.

Build pushes to the main branch and open PRs, but not pushes to other
branches. Allow workflow_dispatch to build them manually if we want to.

#5826)

Extract a couple small duplicate checks into a method, enabling it as a
hook that can be overridden if necessary. It's going to be particularly useful
on a flow I'm working on / testing out, to avoid having to copy over the whole
block of code from the controller to customize it.

We have a similar hook on the registration controller for
`sign_in_after_change_password?`, which was also moved to protected.

While not much practical change, it hopefully shows better the intention
that it's a method users can override if they need, similar to a few
other methods in controllers.

Also move `update_needs_confirmation?` down to private, as this one in
particular I don't think we intended to allow overriding, as it has no
practical behavior change other than the flash message.