SERVER-71823 introduced the basic structure of new checkMetadataConsistency command.

As part of that ticket, the new command was skipped from the jstests:

• jstests/core/views/views_all_commands.js
• jstests/replsets/all_commands_downgrading_to_upgraded.js
• jstests/replsets/db_reads_while_recovering_all_commands.js
• jstests/sharding/database_versioning_all_commands.js
• jstests/sharding/libs/last_lts_mongos_commands.js
• jstests/sharding/read_write_concern_defaults_application.js
• jstests/sharding/safe_secondary_reads_drop_recreate.js
• jstests/sharding/safe_secondary_reads_single_migration_suspend_range_deletion.js
• jstests/sharding/safe_secondary_reads_single_migration_waitForDelete.js

We should investigate if checkMetadataConsistency command must continue skipping those jstests.