The corpus artifacts of the libfuzzer evergreen task must be pushed back to S3 on completion, even if the task fails. However, YAML doesn't let us extend the set of teardown tasks that are generally available, only replace them. We require the default set, in order to inform evergreen of the set of tests we run so that they may appear in the UI.

To make this work, we need to run the libfuzzer teardown tasks unconditionally in teardown for all compile-like tasks, and ensure that they are no-ops unless running with libfuzzer