This reverts commit 6c632dc6

This reverts commit 6324718b.

This reverts commit 3716524b.

Just change all imports and dependencies.

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

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

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

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.

Just use the inherited one set by the user.

to be in line with the logo

This duplicates the language switcher on the tugraz.at site.

Compared to the previous implementation we now show the next language
and use the translations for the next language, so that users only knowing
english can understand it.

In case of more languages we just cycle through them, which isn't ideal but
good enough for now.