fix bug when setTimeout is mocked

[boujeepossum]

tho things:

1. Right now the whole circus thing is going on in the inner scope, meaning the globals like setTimeout are shared with the test and could be mocked (which will mess up circus internals). This is a quick fix to reference the real values before any test files are imported so nothing can mess with them. (i have a task to move circus to the outer scope, it'll take a while though, cause the code that does this right now is very complex)
2. Sometimes tests won't return (exit) until all timeouts are resolved. To avoid this i save the timeout ids and clear them after the test is finished

[codecov-io]

Codecov Report

Merging #3769 into master will decrease coverage by 0.05%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3769      +/-   ##
=========================================
- Coverage   59.86%   59.8%   -0.06%     
=========================================
  Files         191     191              
  Lines        7007    7014       +7     
  Branches        6       6              
=========================================
  Hits         4195    4195              
- Misses       2809    2816       +7     
  Partials        3       3

Impacted Files	Coverage Δ
packages/jest-circus/src/utils.js	0% <0%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92e432a...fd873f2. Read the comment docs.

[cpojer]

I didn't know that was a thing.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.