The aggregation stage is meant to display the entire catalog if run against the admin db.
However, the test does not exhaust the cursor when running $listClusterCatalog.

This is problematic because:

• Previous run of the different core tests are leaving garbage databases/collections around which are displayed by the stage, possibly exceeding the default batch size returned by the stage.
• The catalog entry we are expecting to see in the stage result might not be present in the first batch.

The test should always ensure to exhaust the cursor before comparing the result with listCollection.