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

This happens for example if we access "/dbp-signature.html" in which case the
router interprets the file name as a language.

Register the activity properly and create a scoped element if the API is there.

One all bugs are fixed upstream this should allow us to switch to lit v2
without any further changes.

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)