Fix test and improve process sandboxing

[mjesun]

The native EventEmitter module will not create an _events collection, if there is already an existing one (see code here).

This causes that the existing listeners are not re-initialized in the deep copied process object, so tests triggering listeners will also trigger the original Jest listeners. The fix is simple: avoid copying the _events property so the object gets re-initialized.

Also fixes the ./child test from jest-worker when running in parallel mode.

[cpojer]

Time to turn it into a whitelist? ;P

[mjesun]

I think it's better to break when an option is wrongly copied than silently missing one recently added (unless the blacklist becomes bigger than 5-6 options; in which case I'd agree)

[SimenB]

Hah, such a tiny change

[codecov-io]

Codecov Report

Merging #5027 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5027      +/-   ##
==========================================
+ Coverage   60.35%   60.37%   +0.01%     
==========================================
  Files         198      198              
  Lines        6639     6637       -2     
  Branches        4        3       -1     
==========================================
  Hits         4007     4007              
+ Misses       2632     2630       -2

Impacted Files	Coverage Δ
packages/jest-util/src/create_process_object.js	100% <ø> (ø)	⬆️
packages/jest-environment-node/src/index.js	76.66% <0%> (ø)	⬆️
packages/jest-environment-jsdom/src/index.js	40% <0%> (ø)	⬆️
packages/jest-config/src/index.js	23.8% <0%> (ø)	⬆️
packages/jest-config/src/normalize.js	92.94% <0%> (+2.13%)	⬆️

---

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 94101e9...87edaac. Read the comment docs.

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