Running the `console` and `dbconsole` commands with a regular argument
as the environment's name automatically expand it to match an existing
environment (e.g. dev for development).

This feature wasn't available using the `--environment` (a.k.a `-e`)
option.

People should rather rely on the `-e` or `--environment` options to
specify in which environment they want to work. This will allow us
to specify the connection to pick as a regular argument in the future.

Since 0a4f6009, it's possible to specify a 3-level database
configuration to gather connections by environment.

The `dbconsole` command will try to look for a database configuration
which points to the current environment but with such flavour, the
environment key is flushed out so let's add the ability to specify
the connection and pick `primary` by default to be consistent with
Active Record.

Remove unused `@last`, `@order_clause`, and `@join_dependency`

Fix `create_with` using both string and symbol

Using `@last` and `@order_clause` was removed at 8bb52746 and 90d1524a.
`@join_dependency` was added at b9599502 but it is unused in the first
place.

This is related with #27680.

Since `where_values_hash` keys constructed by `where` are string, so we
need `stringify_keys` to `create_with_value` before merging it.

Because Arel is a private API and to describe `where_values_hash` keys
constructed by `where` are string.

Do not generate unused components contents in `app:update` task

Remove blank lines in setup

Currently, `app:update` generates all contents regardless of the
component using in application.

For example, even if not using Action Cable, `app:update` will generate
a contents related to Action Cable. This is a little inconvenient.
This PR checks the existence of the component and does not generate
unnecessary contents.
Can not check all options in this way. However, it will be able to
prevent the generation of unnecessary files.

Add a test case for overwriting existing condition on associations

Remove extra `.merge!(order: "id")` for `Relation#first` in tests

Fix boolean column migration script

Remove redundant instances of the word 'simply'

Remove redundant instances of the word 'simply' from documentation, on the basis that if it was simple, the user wouldn't be reading the docs

Remove useless `aliased_table_name` in `JoinDependency`

Remove encoding utf-8 magic comment

If `table.table_alias` is not nil, it is enough to use `table` simply.

Fix doc format for `ActiveSupport::Testing::TimeHelpers` [ci skip]

[ci skip]Remove options of javascript_link_tag and stylesheet_link_tag in guides

Merge pull request #29772 from y-yagi/allow_to_edit_secrets_in_mutiple_applications_at_the_same_time

Allow to edit secrets in mutiple apps at the same time

[ci skip] `Response#charset=` uses `default_charset` when `nil` is passed

In encrypted secrets, the tmp file is used as a fixed file
(`secrets.yml.enc` under the tmp directory).
And that tmp file will be removed after process.

Therefore, if edit secrets at the same time with multiple applications,
the tmp file was conflicting.

In order to avoid the above issue, added pid to tmp file.

Since 07e5301e, `Relation#first` will order by primary key if no order is
defined.

Change sqlite3 boolean serialization to use 1 and 0

Fix configuring third-party cache stores such as ActiveSupport::Cache::RedisStore

Broken in 8da30ad6.

fixes a regression introduced at 8607c25b

Extract `FakeKlass` in `relation_test.rb` and `relation/mutation_test.rb`

Enable Layout/EmptyLineAfterMagicComment cop

Fix english for the rescue_from warning [ci skip]

Abstract boolean serialization has been using 't' and 'f', with MySQL
overriding that to use 1 and 0.

This has the advantage that SQLite natively recognizes 1 and 0 as true
and false, but does not natively recognize 't' and 'f'.

This change in serialization requires a migration of stored boolean data
for SQLite databases, so it's implemented behind a configuration flag
whose default false value is deprecated. The flag itself can be
deprecated in a future version of Rails.  While loaded models will give
the correct result for boolean columns without migrating old data,
where() clauses will interact incorrectly with old data.

While working in this area, also change the abstract adapter to use
`"TRUE"` and `"FALSE"` as quoted values and `true` and `false` for
unquoted.  These are supported by PostreSQL, and MySQL remains
overriden.