Currently we don't allow sharding a capped collection, unfortunately, SERVER-95213 describes a scenario where a capped collection can become sharded in 6.0. A customer might not be aware of this, and could upgrade to other versions, where this scenario cannot happen (as can be seen with the attached diffs that can be tested in v7.0 with commit hash f8582b7 and v6.0 with commit hash d2b3603, in order to run the test a 6.0 binary with the failpoint is necessary).

The purpose of this ticket is to add a check to checkMetadataConsistency that detects a sharded collection where the local metadata of the shards contains the capped option.