In moving analyze_shard_key_basic.js to core_sharding tests, found that for some suites the analyzeShardKey command should fail with InvalidOptions for unsupported readConcern or writeConcern, but instead fails with "Failed to find split points that partition the data into 100 chunks with roughly equal number of documents using the shard key being analyzed :: caused by :: The shard key provided does not have enough cardinality to make the required number of chunks of 100, it can only make 2 chunks", code 4952606. This seems to indicate that the checking for invalid read/write concern was somehow skipped.

See this build patch: https://spruce.mongodb.com/version/672517cb5793c00007d30324/tasks
The failing test is in jstests/core_sharding/analyze_shard_key/analyze_shard_key.js