test: fix tests after minitest upgrade

Fixes fallout from e01bf7f8. One `must_be_like` was missed.

Fix an issue with duplicate preloaded records

Address to the warning "DEPRECATED: global use of assertion methods"

Follow up of #37434.

Fix eager load for no :has_many with limit and joins for :has_many

Fix autosave validation context regression

Merge pull request #37353 from lxxxvi/correct-information-about-record-identification-for-form-helper

correct information about record identification in form helper [ci skip]

Deprecate leaking scope in callback block for association relation

Maintain extra joins for string or complex arel conditions

Backport #37228 and #37112 to 6-0-stable

Delay ActionDispatch::Response configuration to load-time

Allow ActionDispatch::Response to be autoloaded

Include connection in cached query notifications

Rational values are move precise than float values so when comparing
rationals values may be off by a few units that are hard to assert
equality. Let's make sure we are comparing the float value with float
values.

Define the `url_options` needed for SytemTest inside the route proxy:

Don't include routes helpers inside System test class:

Inherit from ActiveSupport::TestCase instead of ActionDispatch::IntegrationTest. Active Job automatically mixes its test helper into the latter, forcibly setting the test queue adapter before Capybara starts its app server.

As a bonus, we no longer need to remove the parts of the ActionDispatch::IntegrationTest API we don’t want to expose.

We were using picoseconds as precision but some Ruby implementations
only support up to nanoseconds. Since that much precision was not needed
to test the feature I decreased the precision.

Fixes #37234.

Fixes #37305.

Follow up #37303.

https://buildkite.com/rails/rails/builds/63957#dc16cd12-10a2-435c-9b64-b8332114d92a/981-1293

Use String#+@ before mutating the result of Symbol#to_s

We are seeing some test failures for this test in #37291. It looks like
what's going on is that Puma has changed the output for this command
between 4.1 and 4.2

Previously:

```
...
* Environment: development
* Listening on tcp://localhost:3000
...

```

Now:

```
...
* Environment: development
* Listening on tcp://127.0.0.1:3000
* Listening on tcp://[::1]:3000
...

```

So to get around this, instead of checking the binding address, just
check for the presence of 'Listening' generally like we do on server
start.
Co-authored-by: Neileencodes <eileencodes@gmail.com>

Since the original message is something like this

    expected file ... to define constant A, but didn't

the \S+ captured the comma. A constant name goes there, so [\w:]+ is
enough and won't match the comma.

Better double checked locking in load_schema

This may happen in engines loaded as gems, for example.

Closes #37285.