lookup_unionWith_subpipeline_local_read.js is structured to execute pipelines with subpipelines in various topologies and inspect profiler entries to assert that a certain number of the subpipeline invocations where performed as remote vs local reads. However there are an increasing number of complex race conditions which affect the exact number of local vs remote reads that are done, becoming a cause of non-trivial BFs. But in the majority of cases, we really only care whether local reads were performed or not, we don't care exactly how many there were.

The task of this ticket is to refactor the test to avoid asserting on an exact number of local/remote reads, making it more robust.