Shared libs unit test failures are a chore to debug

[dianabarsan]

Describe the issue
This is due to us implementing shared libs with npm workspaces and workspaces having a known issue of not short circuiting on a script failure: npm/rfcs#575

Right now, if a unit test in a shared lib fails, the dev must scour the whole log to find which test failed, which is cumbersome and very annoying.

Describe the improvement you'd like
Figure out a way to show a generic error when any of the shared libs unit tests fail at the end of the suite.