aggregation_currentop.js verifies the number of connections active in the cluster at a certain point, however, some internal thread (like the one added by SERVER-74107) might be running at that point, causing failures in the test. If we add any feature in the future that does some similar work to the one in SERVER-74107, we'll start having failures in this test. We should change it in a way we don't expect a fixed number of connections, we could for example, find a way to filter out connections that comes from internal operations.