Currently, the analyzeShardKeyNumRanges server parameter can be set to 1. But having one chunk range means that there are no split points to generate. The calculation of the read/write distribution metrics in the analyzeShardKey command currently cannot handle the case where there are no split points since the $analyzeShardKeyReadWriteDistribution stage requires specifying splitPointsAfterClusterTime, which would only be available if there were split point documents to insert.

As part of this ticket, we should add analyzeShardKeyNumRanges to the fuzzer suites.