fix: avoid global writes for self managed sharding COMPASS-8579

[paula-stacho]

https://jira.mongodb.org/browse/COMPASS-8579

Description

Note: I'm not storing the rest of the geoSharding object in connectionInfo, as the managedNamespace part is something we can manage in compass-web and could easily become stale. I don't think selfManagedSharding can become stale, afaik it's decided when the cluster is created.

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)