Context

Most Windows tasks and some other tasks (e.g. "perf" task) are failing on the waterfall and in PR builds right now. It appears that the problem is caused by an error building "pydantic-core":
On non-Windows hosts:

error: the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.13)

On Windows hosts:

ERROR: Could not install packages due to an OSError: [Errno 2] No such file or directory: 'Z:\\data\\mci\\45ad\\src\\go.mongodb.org\\drivers-evergreen-tools\\.evergreen\\orchestration\\db\\pip-install-iuey1qom\\pymongo_46aaef38471d4e8f86a324d0c17beb17\\test\\discovery_and_monitoring\\errors\\non-stale-topologyVersion-proccessId-changed-InterruptedDueToReplStateChange.json'

Note that the Windows error doesn't directly indicate the same failure, but the timing of when both errors started hints that they're related. We'll need to open a separate ticket for the Windows failures if they aren't resolved by DRIVERS-3649.

Definition of done

• Update the drivers-evergreen-tools submodule at ".evergreen/drivers-evergreen-tools" to the latest version once DRIVERS-3649 is closed.

Pitfalls

What should the implementer watch out for? What are the risks?