CI Lint/Test/Test262 workflow

[jfparadis]

This is a different approach to:
#15

It resolves this issues:

• Use Lerna to avoid the need to order the manually workspaces at the top level.
• Use Lerna to also use the same tool as the developer would use.
• Remove the no-bail option.
• Provide individual job results in the PR checks (lint, test, test262)
• Reduce the verbosity of test output (different reporter)
• Simplify test dependencies in compartment-shim

[warner]

That looks just fine. Go for it!

For agoric-sdk, I'm still kinda interested in breaking out the individual package test results in the Actions display (i.e. testing each in a different step). I have an idea about how to deal with the maintenance overhead of that (Agoric/agoric-sdk#579) but I haven't had the time to try and implement it yet. When all tests pass, it doesn't matter much.

I'd say land this and then I'll keep my eyes open for later PR results, and I'll look to see how much work it takes to find a failure in the Actions results. Maybe it's pretty easy, and I shouldn't put much energy into splitting the packages out to separate lines.

[jfparadis]

I've made everything fail fast, so it's always the last line of a job. Example:
https://github.com/Agoric/SES-beta/runs/458829297?check_suite_focus=true