In newer versions there is now a normal method for this which also supports
dynamically added components.

The static version is deprecated and removed in 2.0, so we need to port here.

This has proper support for rollup while providing the same API.

This is what open-wc recommends now and uses in their @open-wc/testing package

Versions: Lit-Element to 2.4.0 and Lit-HTML to 1.3.0

This fixes a typescript problem and allows us to enable type checking
in the typescript-example package (by removing the ts-nocheck comment)

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.

While it's nice to have a fixed chrome version it slows down the yarn install,
downloads a lot of things, and the chrome version depends on various
system packages so one needss to have chromium installed anyway.

This means developers that want to work on tests need firefox and chdomium installed.

Sadly I couldn't find a way to make browsers optional in case the developer
only has one installed.

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.

I couldn't find any breaking changes affecting us

We couldn't do this until now because we referenced them by a relative path with npm.
But now that we reference them by name and yarn handles the linking we can
specify them as normal dependencies.