The bypass_compile_and_fetch_binaries and burn_in_tags_bypass_compile_and_fetch_binaries scripts call out to the evergreen API to get build ids for a given revision. We recently built a python evergreen client and added it to the burn_in_tests buildscript. We should be consistent and use evergreen.py to access the evergreen api everywhere.

Currently, the scripts call this endpoint directly:
https://evergreen.mongodb.com/rest/v1/projects/<project>/revisions/<revision>

Instead, they can use evergreen.py to call this v2 endpoint:
https://evergreen.mongodb.com/rest/v2/versions/<version>

------------------------------------------------------

As a mongo engineer
I want bypass_compile_and_fetch_binaries and burn_in_tags_bypass_compile_and_fetch_binaries to use a common evergreen client library
so that I don't have to maintain code to connect to evergreen.

AC

• The bypass_compile_and_fetch_binaries and burn_in_tags_bypass_compile_and_fetch_binaries scripts do not directly call the Evergreen API

------------------------------------------------------

Related tickets:

• https://jira.mongodb.org/browse/SERVER-40893
• https://jira.mongodb.org/browse/SERVER-41940