When the IndexBuildsCoordinator is enabled on a primary that subsequently steps down while multiple index builds are running concurrently on the same collection, it may be possible for these index builds to deadlock during the clean up phase initiated in IndexBuildsManager::tearDownIndexBuild().