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 reverts commit 6c632dc6

This reverts commit 6324718b.

This reverts commit 3716524b.

Just change all imports and dependencies.

Instead of handling the visibility checks at render time we keep around a list
of visible routes and emit an event when they change. This way the welcome activity
can mirror what the menu shows and update at the same time.

This field specifies a list of roles that the logged-in user needs to
have to interact with this activity.

In the case of the app-shell this means the activity is hidden until
the user information is loaded after login.

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.

Group activity names and descriptions so it's mroe clear what belongs together