feat: add fakeTimersLolex to the test environments

[SimenB]

Summary

In my continuing quest to land Lolex, this PR deals with adding it to the environments. There's no way to activate them, but a user can do

import NodeEnvironment = require('jest-environment-node');

export = class NodeEnvironmentLolex {
  constructor(...args) {
    super(...args);

    this.fakeTimers = this.fakeTimersLolex;
  }
};

and then use that custom environment. A couple of caveats, though - using runAllImmediates will throw since it's not implemented, and there's no way to access setSystemTime

Test plan

Tests added. The PR for actually making it accessible via API will include more tests, this is just threading through.

[codecov-io]

Codecov Report

Merging #8925 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #8925      +/-   ##
==========================================
- Coverage   64.28%   64.28%   -0.01%     
==========================================
  Files         276      276              
  Lines       11711    11715       +4     
  Branches     2866     2868       +2     
==========================================
+ Hits         7529     7531       +2     
- Misses       3550     3552       +2     
  Partials      632      632

Impacted Files	Coverage Δ
packages/jest-fake-timers/src/FakeTimersLolex.ts	69.76% <100%> (ø)	⬆️
packages/jest-environment-node/src/index.ts	48.57% <40%> (+0.08%)	⬆️
packages/jest-environment-jsdom/src/index.ts	39.13% <50%> (+0.49%)	⬆️

---

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 a7f2d0d...c96a3b1. Read the comment docs.

[thymikee]

Should we somehow mark/comment that it's only temporary and not an official API? On the other hand we don't document it yet, so maybe no need to do it.

[SimenB]

It's the same code the api will use

[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.