In WT-8691, we removed the key_consistent write timestamp usage keyword (MDB server never used it, and the ordered keyword is the keyword that MDB server is moving to.

We'd always documented ordered as a superset of the key_consistent checks, but that was not actually the case, there were a number of test checks done inside WiredTiger that were only done in the case of the key_consistent keyword and not for the ordered keyword.

As part of the change in WT-8691, I changed those tests to be run for the ordered keyword, and the MDB build broke.

This ticket switch back to the previous set of checks in order to bring the MDB server build back to green.