In https://jira.mongodb.org/browse/SERVER-82200 , we amended burn_in_test's logic for determining which tests should run. Previously, the test looked at directly affected files. After, the test looked at indirectly affected files.

This had the positive effect of including more likely-to-be-broken tests.

It also had the negative effect of exponentially increasing the volume of tests-to-be-run, which in turn resulted in timeouts and resource exhaustion in Evergreen.

As a result, we've decided (https://mongodb.slack.com/archives/C06FEUUJW2U/p1706293634610059 ) that the drawbacks outweigh the benefits, so we'll revert the change.