Consider the $lookup overload of distributedPlanLogic and constraints. Both methods provide information around shard targeting: while the former determines whether the current stage should be sent to the shards or act as a merger, the latter determines whether we need a merging shard (if any). This ticket tracks the work to refactor this code such that these two parts of shard targeting behavior are not split across two methods.