Since we do not explicitly set a timeout for burn_in generated tasks, a hung test would not fail until the default timeout is hit. This has lead to some timeouts causing large log files to be written and makes it difficult to access the log files. If a given test has test history, we should be able to get an approximation of how long the test should run for and set timeouts dynamically. The "generate_resmoke_tasks" already does this.

As a server engineer,
I want burn_in generated tasks to timeout if they run for too long,
so that the log file for the test stays a manageable size.

AC:

• Every task generated by burn_in that has a test history, sets a timeout based on that test history.