The backup and restore tests in the noPassthrough suite are resource intensive, and that suite is often running out memory (hitting OOM failures). This results in a lot of BFs where we are constantly increasing the size of the variants running the noPassthrough suite, as well as trying to reduce the concurrency to avoid this issue. Unfortunately, whenever changes are made to the suite (tests are added etc, more tests are being run at once) then it is often the backup and restore tests that end up failing since they are using the most resources.

To put guardrails on our evergreen testing to prevent less failures (and save us from constantly having BFs), and also minimise the usage of resources, we should create a new suite for these tests that we are able to manage and ensure it has enough resources to run. 

See if we can reduce the variants on the noPassthrough suite once this is done.