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

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.

We only want to export it in the package entry point and not
the generated bundle.

The demo now registers our web components lazily with a unique name
so that two different apps using the same underlying web compontens
don't clash.

This also disables auto registering and leaves that to the user.

So we get errors with older browsers.

Also use the same reference for removing the event handler, bind creates a new one.