Suggestion

This is explained already in #10582 but the summary is as follows:

We currently enable coverage in our test scripts and pass coverage=false when we want to disable it

This results in jest --coverage --coverage=false once everything is expanded

The duplicate flag works in jest but doesn't seem right. More importantly, it does not work with vitest (which we may soon want to move to).

We can solve this by having two scripts in each package:

• test with coverage disabled
• test-coverage with coverage enabled (if the package supports coverage)

CI can then call test-coverage instead of manually passing flag overrides

Additional Info

No response