In case the path ending with the activity ID has more trailing path elements, we don't fall
back to the default route but just ignore them (and save them in the router state).

This allows passing in extra information via the path without breaking the routing,
and in case we want to forward the routing to the activities in the future we can use
the extra path elements we store for that.

For this to work with our current logic we have to stop comparing path strings and compare
the resulting computed state everywhere instead.

This got added in scoped-element 2.1.0 and is more or less the same
as getShadowRootDocument()

In case the scoped registry polyfill is loaded we need to create
elements inside of the shadowroot.

getShadowRootDocument() returns the polyfilled shadowroot, or in case
the polyfill is not loaded just return the global document, which works
in case there are no scoped registries.

In case we get something like https://github.com/open-wc/open-wc/pull/2389
this will be usefull. Also it makes IDE completion work + eslint.

This reverts commit 6c632dc6

This reverts commit 6324718b.

This reverts commit 3716524b.

Just change all imports and dependencies.

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.

In case the activity emits this event then we switch to the specified activity.

This reverts commit 421d92f3.

In case the current state is the default one we don't redirect.
This gets rid of the initial redirect/histroy entry when loading the page.

If the current state can't be used to generate a path just fall back
to the current path

Use a dbp-rpovider in the app shell to use the attributes auth, requested-login-status and analytics-event only locally