With the introduction of SERVER-49228 it is possible that we will attempt to register collection sharding state for a views underlying collection more than once, in the case that after the first registration we find that we our config state is uninitialized and need to reload / retry the command. This will trigger an invariant in OperationShardingState::initializeClientRoutingVersion that confirms that the given namespace does not already exist in _shardVersionsChecked.

To address we should relax this invariant to only trigger when the registered collection is also registered as sharded.