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

This prevents eslint from traversing the parent directories. In
the case there was a conflicting eslint config in a parent directory it would
error out otherwise (like is the case in our apps)

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

Use "language" instead of "lang" because "lang" seems to be handled specially in html elements (dbp/apps/library#77)

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

Implement "set-property" handling in dbp-provider and use it in dbp-language-select (dbp/apps/library#77)