The evergreen.yml file has lots of task and task group names that are primarily historical and only loosely associated with what they actually do.

Additionally, some tasks like unittests both compile and run the unit tests, making it hard to know whether to attribute slowness to the compile part of the task, or the test execution part of the task.

Refactor these names to coherently describe what each task or task group does. Notably, we should not have any task called merely compile, as it is too hard to search for, or understand what it actually does (hint: it currently does no compiling).