This event gets dispatched in case the CSP blocks something.
This is motivated by browsers handling this differently, for
example spawning a worker via blob: is allowed in chrome, but not in firefox
and things like "worker-src" is not supported in safari..

So having some error reporting there is helpful in case some browser
version somewhere behaves differently.

In greenlight we copied this code for scanning images, either from
real image files, or from PDF files converted to images via pdf.js.

To avoid duplication clean up the internal API and expose it.

Also write some unit tests for the scan engine while at it.

Multiple changes:

The worker can now be auto-bundled via rollup and no longer has to be passed manually.
This is handled via a js script file which builds a blob containing bundled code.
This requires some CSP exceptions in the target applications, so mention that in the README.

scanImage() now takes an option object and defaults to returning more information, so
handle both changes (returnDetailedScanResult now defaults to true)

Component users can now drop their worker copying code and need to adjust their CSP.

1.4 and newer no longer detect any QR codes for some reason.
Needs to be investigated why..

Squashed commit of the following:

commit 21309f2c
Merge: f69672e8 7a2e492e
Author: Manuel Kocher <manuel.kocher@tugraz.at>
Date:   Thu May 12 14:16:56 2022 +0200

    Merge branch 'master' into dbp-translation-component

commit f69672e8
Author: Manuel Kocher <manuel.kocher@tugraz.at>
Date:   Thu May 12 13:48:10 2022 +0200

    Remove unnecessary en translation text

commit 6d0df984
Author: Manuel Kocher <manuel.kocher@tugraz.at>
Date:   Thu May 12 13:36:45 2022 +0200

    Remove unnecessary imports and minor refactor

commit 6496d910
Author: Manuel Kocher <manuel.kocher@tugraz.at>
Date:   Thu May 12 13:24:51 2022 +0200

    Add lang-File attribute to README

commit 7a528144
Author: Manuel Kocher <manuel.kocher@tugraz.at>
Date:   Thu May 12 13:17:40 2022 +0200

    Add dbp-translation component and include it in showcase

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.