The sh.status() and db.printShardingStatus() shell helpers both call the getPrintableShardingStatus mongosh function.
This function is fairly complicated and does a bunch of aggregations and data manipulations to create the sh.status() output. The goal of this ticket is to analyze the getPrintableShardingStatus logic and figure out if we could introduce some new commnad/aggregation stage to simplify the gathering of this information.

Exposing those intermediate commands would allow customer to retrieve this information more easily also from other drivers (aka outside of the mongosh)