This makes problems with the new scoped elements polyfill, which now correctly
makes globally registered elements not visible in the shadow roots. Instead
we have to add the tempaltes at the level of the templates so they get their
global web components and only then transplant them into the light dom of the
nested web components with their own registries.

This reverts commit 3716524b.

Just change all imports and dependencies.

Instead of throwing an error.

So the login process completes, but the user will not have any roles in that case.
This helps in case the API isn't set up but the user wants to try the frontend app.

We still need to force the v3 format internally because i18next-scanner
doesn't support the new format and v4 drops support for Safari<13.

By setting compatibilityJSON things should continue to work as before.

Remove any mention of TU Graz.

Since this is very simple JS code and we can't adjust it with
slots etc. just remove the support text.

port to firstName/familyName

We still want to finish the auth process in that case, so the app
can display some error message.

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

In case of the server template there are no enpoints registered by default,
but we still sue the keycloak login in the API docs. To avoid errors there
gracefully handle that case.

This way we can depend on the roles being available when the login is done.

auth.person-id is now deprecated, auth.user-id should be used instead

auth.person is now deprecated and only contains a list of roles. There is good replacement
for this at this point.

_setLoginStatus takes care of that anyway.

We now enable it by default for everyone. The plan is to load the API
user instead and not the person as a next step. This api should work
even for users that don't have a person associated.

This is the only place this information is used and we want to
clean up the API. Since this is more of a demo component and not
activitely used anywhere anymore just remove it.

This removes the 'show-image' (false by default) and removes the functionality
to show a user profile image in the logout dropdown.

We've never used this actively and want to clean things up, so remove it.