This test in lookup_unionWith_subpipeline_local_read.js assumes that the primary shard will execute a subpipeline of the $graphLookup first. But if the non-primary shard executes a subpipeline first, it targets the primary which must do a refresh. Then, by the time the primary shard executes its first subpipeline, it already has the relevant information about the collection and doesn't need to target shards.

We should change the test to allow for both cases and audit for other related issues in the same file.