Tracking issue: stabilization of test runner code coverage

[cjihrig]

What is the problem this feature will solve?

This issue is for tracking remaining work to stabilize code coverage in the test runner. When this feature originally shipped, it had documented limitations. Those have all been resolved.

Note that stabilization does not prevent future semver-minor additions or bug fixes.

Here is the minimum list of things that I think need to be resolved:

• [ ] Coverage should be supported via the run() API.
• [x] lib/internal/test_runner/coverage.js should not call parseCommandLine(). The flags should be passed in. This is related to https://github.com/nodejs/node/issues/53867.
• [ ] --experimental-test-coverage is replaced/aliased with --test-coverage

What is the feature you are proposing to solve the problem?

Eventually stabilizing test runner code coverage

What alternatives have you considered?

No response

[cjihrig]

cc @MoLow @atlowChemi @benjamingr if you have other things to add to the list.