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 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.

We match based on the tag name now and not on the namespace,
so revert this again so it's consistent with the other packages

So we only need to define it in one place.

Just to test if/how this works.
It now uses "dbp-auth" instead of "translation", which was the i18next default.

It always seems like the button is missing when loading the page and
expecting the button there based on experience.

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)