These are all transitive dependencies (or unused) so they get pulled in
anyway.

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.

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

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 is used in various packages, so clean it up and add it
to rollup.utils.js.

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.