Currently, evergreen test reports are produced by running buildscripts/create_bazel_test_report.py which examines XML reports that bazel test produces. By default, bazel is aware of gtest and will suppress its own XML reports and allow gtest to produce its own. The logic in create_bazel_test_report.py doesn't work will with the gtest reports; because it is highly sensitive to bazel's format, it will often crash when running against gtest reports and produce no results or incomplete results.

Adapt the evergreen test reporting infrastructure to produce consistent, accurate, complete and navigable reports when tests run on gtest.