• clients/test/extension/popup-test.js
• clients/test/extension/settings-controller-test.js
• clients/test/lightrider-entry-test.js
• docs/recipes/integration-test/example-lh-auth.test.js

well, these are covered by yarn test-clients and yarn test-docs in ci.yml. I'm pretty fine running them with yarn unit if they're going to be listed in the jest.config.js, though.

Context here is that #13146 is adding yet another directory with tests in it, and I don't really have any interest in adding a yarn unit-shared with bonus && yarn unit-shared and && npm run unit-shared -- --ci when yarn unit could just run them all and yarn jest shared works just fine for narrowing to just those tests already :)

rather than make docs/recipes/integration-test/example-lh-auth.test.js work in the unit tests, would rather just remove it from the unit tests (#13150)

updated with docs test changes from #13150 so yarn test-docs doesn't run under yarn unit.

Also moved the *-test-pptr.js tests previously identified as flaky (they have automatic retry in CI) out of the default unit tests. They now only run under their respective yarn test-clients/yarn test-viewer/yarn test-treemap and not under yarn unit, which is exactly the current behavior.

fraggle-rock/**/*-test-pptr.js has been running in unit.yml without flakes for a while now, so seems ok to leave under unit tests (for now?).