SERVER-116390 made it such that randomly, in 1% of cases, commands with remote aggregations (for subpipeline stages $lookup, $unionWith) now return DataBearingNodeMetrics which are incorporated in the PlanSummaryStats.

This is reflected in the explain(executionStats) and system.profile.

The above two tests have become unstable now, since they assert on these values.

We can use an always on/always off stats sampling override in them.