After SERVER-81231, the output of the serverStatus command reports the sharding.clusterRoles key containing the list of roles actually acted by the node (e.g., router, shard, config).

This new key reflects the actual configuration of the process (ClusterRole). Unfortunately, in case of a config server, the node apparently acts a shard, so the serverStatus command returns incorrect information.

Determining whether a shard also acts as a config server is relatively complex, as the status is based on a dynamic property — whether the user has executed a transition commands or not.

The original idea was to extend the serverStatus command to provide to Atlas InTel an easy way to determine whether the embedded router is enabled or not. As a consequence, the goal of this ticket is to remove the sharding.clusterRoles key and add the sharding.routerServiceEnabled key (set to true or false).