The current multi-collection acquire path offered by AutoGetCollectionForReadLockFree violates a fundamental sharding requirement that all referenced namespaces pre-declare a placement concern (db or shard version). Because of this, they are not safe to use with a concurrent shardCollection or movePrimary.

This ticket is to switch the two usages in DocumentSourceCursor to the new acquisitions API.