See https://github.com/emn178/js-sha256/issues/18

Instead of fetching it from the configured keycloak server.

We had this initially, but switched to the server variant to make
sure we are always compatible with the keycloak version.

Now upstream keycloak has deprecated this strategy and in Keycloak 22
the server provided js bundle will be removed.

So switch back to the npm package.

The old version is no longer maintained and doesn't support rollup v3

Up until now it would throw and never set a login status. This would lead
to the login process never completing, and in our case the app-shell
would never show the app and only show a white page.

Instead set the status to logged out and show a notification.

It has new API which we want to use.

Newest Ubuntu switched Firefox to a snap, which breaks karma.

Try to use playwright to download and cache firefox/chromium
and use those for karma.

Compared to puppeteer where we did this some time ago this caches
the browsers globally, and only downloads them when we start the tests.

This reverts commit 6c632dc6