After SERVER-57003, task generation will be split into 2 phases: the actual creation of the tasks and the activation of the tasks. The activation step is fairly straightforward and shouldn't require a lot of setup. However, the standard setup for server tasks performs a lot of unneeded work (cloning the repo takes around a minute alone). We should optimize the task setup for activated tasks, since they will be a lot of them run still.

As an engineer,
I want task activation to be as fast as possible,
So that the resources activate the tasks can be used for other tasks.

AC:

• Most of the time in the activating tasks in spend making evergreen api calls.