fix: remove support for runScript

[SimenB]

Summary

It cannot be used for ESM anyways, so let's clean up our code a bit

Test plan

Green CI

[SimenB]

should we warn if runScript is present? Might make it harder for a single test env to support multiple versions of Jest, bt also less confusing than "why isn't my code running"

[codecov-io]

Codecov Report

Merging #11155 (a999062) into master (fedafc3) will increase coverage by 0.02%.
The diff coverage is 30.00%.

@@            Coverage Diff             @@
##           master   #11155      +/-   ##
==========================================
+ Coverage   64.19%   64.21%   +0.02%     
==========================================
  Files         307      307              
  Lines       13372    13369       -3     
  Branches     3260     3258       -2     
==========================================
+ Hits         8584     8585       +1     
+ Misses       4083     4081       -2     
+ Partials      705      703       -2     

Impacted Files	Coverage Δ
packages/jest-environment-node/src/index.ts	61.11% <ø> (+4.70%)	⬆️
packages/jest-runner/src/runTest.ts	1.92% <0.00%> (-0.12%)	⬇️
packages/jest-runtime/src/index.ts	55.76% <66.66%> (+0.17%)	⬆️
packages/jest-environment-jsdom/src/index.ts	39.13% <100.00%> (+1.13%)	⬆️
packages/expect/src/utils.ts	96.12% <0.00%> (+1.29%)	⬆️

---

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 fedafc3...a999062. Read the comment docs.

[SimenB]

Will merge after we land the website update

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