SERVER-74416 made mongos explicitly attach a readConcern to the analyzeShardKey command that it forwards to a shard. That only makes the analyzeShardKey performs the database and shard versioning check before it starts executing. Data placement changes can occur after the command starts executing. So all the aggregate commands (**) that the analyzeShardKey command run internally must also explicitly attach a readConcern to opt into database and shard versioning.

(**) The aggregate command for calculating the cardinality and frequency metrics for a non-unique shard key can continue to use readConcern "available" due to the performance reasons related to shard filtering as detailed in the design.