Avoid a spurious deprecation warning for database URLs

This is all about the case where we have a `DATABASE_URL`, and we have a
`database.yml` present, but the latter doesn't contain the key we're
looking for.

If the key is a symbol, we'll always connect to `DATABASE_URL`, per the
new behaviour in 283a2edec2f8ccdf90fb58025608f02a63948fa0.

If the key is a string, on the other hand, it should always be a URL:
the ability to specify a name not present in `database.yml` is new in
this version of Rails, and that ability does not stretch to the
deprecated use of a string in place of a symbol.

Uncovered by @guilleiguaran while investigating #14495 -- this actually
may be related to the original report, but we don't have enough info to
confirm.
Avoid including DB details in exception messages

The keys are quite sufficient; we shouldn't be throwing passwords
around.
Fix default_url_options example in i18n guide [ci skip]
Merge pull request #14564 from killthekitten/patch-2

Fix default_url_options example in i18n guide
In Active Record Querying guide, currently `Merging of scopes` section uses a concept of default scope in its example before it is introduced in the following section titled `Applying a default scope`.

It makes more sense to switch the ordering to introduce default scopes (`Applying a default scope`) first and then go into `Merging of scopes` section where it is used.
Add ConnectionHelper to refactor tests.
Merge pull request #14576 from ariabov/scope_sections_reordering

Change order of scope subsections in Active Record Querying guide [ci skip]
Treat blank UUID values as nil
Merge branch 'lavrovdv-patch-1'
Merge pull request #14561 from tgxworld/refactor_run_without_connection

Add ConnectionHelper to refactor tests.
Merge pull request #14570 from matthewd/uri_deprecation_warning

Avoid a spurious deprecation warning for database URLs