Leave all our tests as order_dependent! for now

We're seeing too many failures to believe otherwise.

This reverts commits bc116a55ca3dd9f63a1f1ca7ade3623885adcc57,
cbde413df3839e06dd14e3c220e9800af91e83ab,
bf0a67931dd8e58f6f878b9510ae818ae1f29a3a, and
2440933fe2c27b27bcafcd9019717800db2641aa.
[ActiveJob] TestCase (Will squash before merge)
Merge pull request #16724 from seuros/testcase

[ActiveJob] TestCase
Add and Remove string/strip require

Method .strip_heredoc is defined in
active_support/core_ext/string/strip.rb so we need to require it.

[fixes #16677]
Merge pull request #16770 from arthurnn/add_string_strip_require

Add and Remove string/strip require
Remove '*' which doesn't work

I found an * does not work in Markdown notation. It should be removed.
Merge pull request #16772 from satoryu/master

Remove '*' which doesn't belong [ci skip]
Clarify Rails uses erubis not stdlin ERB. [ci skip]
Merge pull request #16773 from cirosantilli/erb-erubis

Clarify Rails uses erubis not stdlin ERB. [ci skip]
Shorten ActionView::Base doc summary line. [ci skip]
Merge pull request #16774 from cirosantilli/erb-erubis2

Shorten ActionView::Base doc summary line. [ci skip]
Merge pull request #16762 from eileencodes/refactor-add_constraints-complex-loop-conditional

Refactor add_constraints complex loop conditional
Add a quick straw-man Incompatibilities section

Is this a thing we want?

Note current duplication between the `assert_select` section here, and
the corresponding release note entry... does this detail *move* from
there to here?

[ci skip]
Remove 'if exists' from drop table statement then use `table_exists?`

Since 'drop table if exists' statement does not always work with
some databases such as Oracle.
Fix failing tests in ActiveJob Adapter
Merge pull request #16778 from yahonda/if_exists

Remove 'if exists' from drop table statement then use `table_exists?`
Merge pull request #16777 from seuros/testcase

Fix failing tests in ActiveJob Adapter
use correct operator in query based on JSON document
Move column option handling to new_column_definition

TableDefinition#column is not called from `add_column`.
Use TableDefinition#new_column_definition for column option handling.
Dont mess with default order engines load

When copying migrations some engines might depend on schema from other
engine so we can't blindly reverse all railties collection as that would
affect the order they were originally loaded. This patch helps to only
apply the order from engines specified in `railties_order`