Actually `StatementCache#execute` is always passed the same klass that
the owner klass of the connection when the statement cache is created.
So passing `klass` to `StatementCache.new` will make more DRY.

Handling add/remove to/from migration edge cases 

Update String#camelize to provide feedback when a wrong option is sent

Making sure the table name is parsed correctly when an add/remove column migration have 'from'/'to' in the table name.

Allow non-English values for collection_radio_buttons

Use File::NULL instead of "/dev/null"

`Relation::Merger` should not fill `values` with empty values

Fix `find_by` with range conditions

Unlock minitest for Rails' test suite

Refactoring `Response#charset=`

Sync transaction state when accessing primary key

String#camelize was returning nil without any feedback when an
invalid option was passed as parameter. This update makes the method
to raises an ArgumentError when the option passed is invalid, similar
to what Ruby does for String#downcase (and others) in 2.4.1.

https://ruby-doc.org/core-2.4.1/String.html#method-i-downcase

Use duktape gem as default JS engine on Windows-MINGW

The fallback javascript engine on Windows is Windows Script Host (JScript).
However this engine isn't able to process the default assets, because it supports
ES3 only but the coffeescript compiler requires ES5.

Fixes #30014

Since this test changed in 92209356 I noticed that it really doesn't make
sense anymore. I split the tests into 2 groups to explain what each one
does.

First these routes should throw a `bad_request` when the encoding isn't
valid. We're expecting UTF8 encoding and passing binary, that should be
a bad request.

For the second test we are setting the `show` route to set
`self.binary_params_for?` for that route which will convert the
parameters and return a `:ok` instead of a `:bad_request`.

Remove unnecessary `doc` directory deletion

This commit changes the behavior such the path_params now default to
UTF8 just like regular parameters. This also changes the behavior such
that if a path parameter contains invalid UTF8 it returns a 400 bad
request. Previously the behavior was to encode the path params as binary
but that's not the same as query params.

So this commit makes path params behave the same as query params.

It's important to test with a path that's encoded as binary because
that's how paths are encoded from the socket. The test that was altered
was changed to make the behavior for bad encoding the same as query
params. We want to treat path params the same as query params. The params
in the test are invalid UTF8 so they should return a bad request.

Fixes #29669

*Eileen M. Uchitelle, Aaron Patterson, & Tsukuru Tanimichi*

[ci skip] Fix rails_command comments

Fix rubocop issues

Remove redundant `unless current_adapter?(:OracleAdapter)`

Since 553b6958, `doc` directory is not created in application.

[ci skip]

Closes #30012

And make reference to `Relation`.

Fix typo in assert_changes error message

Merge pull request #30016 from albertoalmagro/set-ruby-version-in-gemfile-and-ruby-version-by-default

Set Ruby version in Gemfile and .ruby-version by default

Avoid duplicate clauses when using #or

Fix test directory to correct path

Fix testing helpers that use Action View's capturing helpers (e.g. content_for)

[ Orhan Toy & Kasper Timm Hansen ]

Fix `warning: method redefined;`