When the new primary shard is changed, the entire document in the config.databases collection, implicitly setting the unset fields to their default value, i.e., `partitioned` to `false`.

This problem has no practical effect for end users since the `partitioned` filed it not longer used starting from `6.0` branch. However, this field must be properly managed until it is removed.