SERVER-138004ClosedFixed
suppress LSAN failure due to mongo client shutdown order
<https://jira.mongodb.org/browse/BF-46959> so far looks like it's spurious, due to the order in which threads terminate in the mongo test driver. At least according to AI. This ticket is the work of looking into more closely, and either adding a LeakSanitizer (LSAN) exception to silence the failure, or making a code change to fix a real underlying leak or shutdown race.