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

Use tdd in all cases to be more consisstend.
Also since last year we can use chai with rollup directly, so
do that everywhere instead of relying on karma-chai injecting
it in to the global scope.

Now that we have a separate component for keyclaok we can move those
keycloak specific settings into their own attributes.

This should make it more clear what the components are used for

vpu-auth listens to login/logout events which the button emits
and the button shows data from the auth-update event.

We don't want to depend on harcoded values in the build

Also run tests in gitlab-ci