Change DistLock initialization so each node in a shard will have the same ID when locking

When initializing the shard components, a new ID is generated for the distributed lock, however, if a primary node holds a lock and a stepdown happens, then when trying to hold a lock over the same resource (when retrying the operation) will fail.

As part of the PM-1965 project, the shardCollection command will be moved to the primary, and the current behavior will not allow this necessary change.