It has new API which we want to use.

Newest Ubuntu switched Firefox to a snap, which breaks karma.

Try to use playwright to download and cache firefox/chromium
and use those for karma.

Compared to puppeteer where we did this some time ago this caches
the browsers globally, and only downloads them when we start the tests.

This reverts commit 6c632dc6

This reverts commit 6324718b.

This reverts commit 3716524b.

Just change all imports and dependencies.

No longer needs babel, but requries an alpha version of the typescript plugin
for eslint 8 support

Instead of using the namespace which is hardcoded we use the tag name that was
used to register the element (or the "real" tag name in case of a scoped element).

This way if AppShell is regsitered as "dbp-some-app" it can still be overriden by
specifying "dbp-some-app" in the overrides object.

We need a separate i18next instance per component instance and
call setOverrides() to override the translations.

Uses a separate namespace that gets used over the default one, so we can override,
but also remove the overrides again when needed.

This has the problem that all clones have the same store, so this overrides
the translations for all clones and not just the one providing the overrides.

It was missing a provider element

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