When an engineer tries to repro a test failure, they sometimes add a large resmoke_repeat_suites number to evergreen.yml. This causes generated tasks to compute a large Evergreen timeout and potentially leaving a host running for a long time.

We should cap the runtime of generated tasks and either error out and inform the user of the max repeat number they can use, or interally reduce the repeat count to a smaller number.

Almost always, if an issue fails to repro after 48 hours, it's unlikely for the repro to happen at all. This can indicate a bug with the way the repro is set up, or something wrong with the machine the original failure occurred on.

AC:

• Fails tasks that we expect to run over the specified time limit.
• Provide a message to the user explaining why that task was failed and what they can do if they want to work around it.