Motivation

Log output in Evergreen tasks is very verbose and difficult to parse through. This adds to development time when inspecting test failures on Evergreen to determine the root cause.

Scope
TBD. Investigate what non-essential logs can be removed.

This need not be exhaustive. Consider the following:

1. MONGOC_TEST_MONITORING_VERBOSE is enabled in run-tests.sh. This logs command monitoring events on most specification tests. This is sometimes useful for debugging an individual test failure. It is not useful on passing tests.

2. MONGOC_TEST_SERVER_LOG is enabled in run-tests.sh. This logs all mock server commands and replies. This is sometimes useful for debugging an individual test failure. It is not useful on passing tests.

3. The excessive amount of warnings in the debug-compile-c89 task often makes it difficult to identify a C89 warning that triggered an error in that task.

4. libmongocrypt is built as part of the compilation process: https://github.com/mongodb/mongo-c-driver/blob/96ed1d70210ec5096aaeab0adbb5ae4323291f20/.evergreen/compile-unix.sh#L215:L227 libmongocrypt could instead be fetched from the uploaded tarballs at https://s3.amazonaws.com/mciuploads/libmongocrypt/all/master/latest/libmongocrypt-all.tar.gz instead of built from source.

5. The "prepare kerberos" function in the "pre" tasks produces errors on platforms that do not succeed with that setup.