chore(monorepo): run jest on all frontend projects by default

[shlokamin]

Overview

So it turns out that jest's watch cli flag only works as expected (only rereuns tests that your code change affects using a dependency graph) if you don't provide specific test file paths.

i.e. yarn jest --watch will only run tests that your src code change affects, while yarn jest step-generation --watch will rerun ALL step generation tests when a file change is made even if the file you modified is inside of the app directory.

To fix this, rather than providing paths to all JS projects by default, we run yarn on everything unless file paths are provided.

Good catch, @brenthagen!

Risk assessment

Low

[codecov]

Codecov Report

Merging #13834 (c8479ff) into edge (32dd347) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             edge   #13834   +/-   ##
=======================================
  Coverage   70.76%   70.76%           
=======================================
  Files        2485     2485           
  Lines       69807    69807           
  Branches     8471     8471           
=======================================
+ Hits        49396    49401    +5     
+ Misses      18413    18408    -5     
  Partials     1998     1998           

Flag	Coverage Δ
app	68.24% <ø> (ø)
components	63.01% <ø> (ø)
g-code-testing	96.44% <ø> (ø)
hardware	56.69% <ø> (+0.05%)	⬆️
hardware-testing	∅ <ø> (∅)
notify-server	89.13% <ø> (ø)
shared-data	74.00% <ø> (ø)
system-server	96.02% <ø> (ø)
update-server	63.51% <ø> (ø)
usb-bridge	76.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

[sfoster1]

ah, nice!