The evergreen unit test task has a few issues with respect to targets that fail compilation:

• Tests that fail to compile cause the entire compilation operation to end early because --keep_going isn't passed to the bazel invocation; these report "no status."
• Tests that fail to compile don't show up in the test report.
• Tests whose compilation is skipped due to prior failures don't show up in the test report.

Notably, the whole task still fails if a test fails compilation, so we aren't surreptitiously missing failures; these are concerns about the convenience of discovering and understanding CI failures.

We should pass --keep_going to ensure that we report as many results as we can and report "FAILED TO BUILD" from the bazel report as "failures" in evergreen. We may want to also report "NO STATUS" as something in evergreen, just to ensure there's visibility into those situations.