This way we can extend the message with more data in the future if needed.

In case we move it out of view and back again we want a second event. The user can filter those
out if needed.

We need to give feedback to the user, so better let the user decide.

We use it for user feedback now, so there is no good reason to allow disabling it.

This allows us to show feedback to the user by coloring the clip border.
Also in case there is no match we don't send an event.

There is no need to emit the same thing 5 times a second.

fewer confusing callbacks..

We would get two scanning loops both scanning for qr codes. This makes
sure only one loop is active at all times.

This reverts commit 3c5c82f9.

so they can be reused

This API isn't suported in any browser we support, it used to work in
old chrome.

qr-scanner: only check max 5 times per second for a QR code

See merge request !4

Still raw the image and everything all the time to keep the experience smooth.
One more improvement would be to also skip the image data extraction, but that can
be done after the clipping work.

We no longer bundle keycloak-js with rollup so we can remove those
special cases.

This makes sure the library version works with the server version.

Ideally we'd also want to check the version so we can error out if a too
old keycloak server is on the other side, but I don't see any public API changes
that would allow us to know if the library is too old.

Fixes #32

See #32