After SERVER-94816, tests will only be run in the most complex suite in an ancestral chain of suites on patch builds. We need to make sure that when a suite is disabled but not deleted, this doesn't cause the test hierarchy tool to incorrectly calculate which tests can be run. For example, if suiteAB > suiteA in terms of complexity, then some test t running on suiteAB need not run on suiteA.

However, suppose we temporarily disable suiteAB in the Evergreen YAML file without deleting the original suite YAML file. The test hierarchy tool shouldn't incorrectly stop running t on suiteA because it assumes that t will be run on suiteAB.

We need a linter to prevent this scenario - any suites in the hierarchy definition should be running on Evg.