Use Case

As a... node developer
I want... ci builds to timeout in less than 2 hours
So that... we can save time/money

User Experience

• Currently tests can leak resources and cause a task to timeout after 2 hours. This is despite our usage of `timeout_secs: 300` in evergreen config. We have the timeout configured incorrectly, the property is set at the wrong level. Once we move the property to the same level as `params`, timeouts will start to apply.
• Currently CI build logs "Set idle timeout ... to 2h0m0s." which is the default. None of our timeouts show up in the logs.

Dependencies

• none

Risks/Unknowns

• The current timeouts are going to turn out to be too short in some cases and will cause build failures. We will run all the tests as part of PR/testing to verify that the new timeouts are long enough.

Acceptance Criteria

Implementation Requirements

• `timeout_secs` properties are moved to their correct locations
• all CI builds pass, even with the lowered timeouts
• CI build logs something other than "Set idle timeout ... to 2h0m0s."

Testing Requirements

• CI is green

Documentation Requirements

• none

Follow Up Requirements

• none