[Testing guide] Use "Fixtures API" instead of "fixture api".
[Testing guide] Using "Fixtures API" consistently

- In guides, "API" is used consistently instead of "api".
- Reason behind replacing "fixtures API" to "Fixtures API" is because
  here we are referring to the concept of "fixtures". In other places in
  the guide "fixture" OR "fixtures" is referred to the single or
  multiple instances of test data.
- This is also followup of https://github.com/rails/docrails/commit/aa9d1332b20305dd860b21a7ada06c5252bebad5#commitcomment-8497376.
Fix grammar on ActiveRecord::AttributeMethods doc.

[ci skip]
allow 'all' for :domain option in addition to :all
Don't remove mailer layouts files
Remove custom errors page section from the guides

This pattern is too problematic and introduces a lot of edge cases:

  * On 4.2, the issue https://github.com/rails/rails/issues/15124 is
    back again.
  * needs to define each action for each http status otherwise the
    router raises ActionController::RoutingError (No route matches).
  * If the router has `match "/*username",...` and some action is
    missing, Rails will pick up the "match" and try to do its job.
  * encourages people to copy & paste programming. Not DRY.

[ci skip]
Fix Sidekiq ActiveJob integration setup

* .connect on a Redis connection wasn't valid
* Reset logger after we're done testing for redis connection to avoid
  "closed stream" error when starting server for real from a fork
Hide potentially sensitive ActiveJob params from logs

* Show GlobalID instead of full object .inspect output
Merge branch 'master' of github.com:rails/rails
Only filter GIDable objects; remove cosmetic changes
Removed use of mocha in the info_controller tests
skip test to get `sqlite3_mem` suite passing.
fixing mailer previews for apps with globbing route
document that `.delete` does work on `#readonly?` records. Closes #11860

[ci skip]

This is due to the fact that `.delete` is directly translated to SQL.
It tries to follow the same rules as `.delete_all` which is not able
to verify that records are `#readonly?`.
Failure to rollback t.timestamps when within a change_table migration

When running the following migration:

    change_table(:table_name) { |t| t/timestamps }

The following error was produced:

    wrong number of arguments (2 for 1) .... /connection_adapters/abstract/schema_statements.rb:851:in `remove_timestamps'

This is due to `arguments` containing an empty hash as its second
argument.
Move PredicateBuilder instantiation to constructor

In order to maintain thread safety and prevent race condition from memoization.
Merge pull request #17651 from CLUSTERfoo/fix/adding_timestamps_migration_not_reversible

Failure to rollback t.timestamps when within a change_table migration
docs, add new changelog entries at the top :sweat: [ci skip] #17651
Active Record changelog needs to keep pointing at 4-2-stable. #17651

[ci skp]
Merge pull request #17898 from mrgilman/move-predicate-builder-to-constructor

Move PredicateBuilder instantiation to constructor