And adjust for the import changes

This makes it use those packages from npm instead of locally, not
sure why this was added.

It's confusing that there are two lock files in this repo and two
overlapping workspaces. Ideally everything should be in sync.

lerna complains about this

And remove the custom publish commands

Add a scope so we don't have to care about naming conflicts
and set the verison to 0.1.0 since we don't have a stable API yet.

Chromium sometimes hangs when multiple karma runs happen
at the same time :(

Use tdd in all cases to be more consisstend.
Also since last year we can use chai with rollup directly, so
do that everywhere instead of relying on karma-chai injecting
it in to the global scope.

Using lerna with npm breaks various npm commands such as "outodated"
etc.

Switch yarn with namespaces. lerna is only used to run commands on all
packages and maybe publish them etc. yarn 2.x has extra workspace features
like running commands for all packages, so with 2.0 we might also get
rid of lerna.

They are not published yet