Add a scope so we don't have to care about naming conflicts
and set the verison to 0.1.0 since we don't have a stable API yet.

While it's nice to have a fixed chrome version it slows down the yarn install,
downloads a lot of things, and the chrome version depends on various
system packages so one needss to have chromium installed anyway.

This means developers that want to work on tests need firefox and chdomium installed.

Sadly I couldn't find a way to make browsers optional in case the developer
only has one installed.

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.

We no logner use that library and the "qr-scanner" altternative turned out to
be better, so remove it completely.

With both being async it's hard to follow what would happen if both run at the same
time, so just prevent it and serialize start/stopping instead.

I couldn't find any breaking changes affecting us

It's a webpack plugin, so unlikely that it is used.

We couldn't do this until now because we referenced them by a relative path with npm.
But now that we reference them by name and yarn handles the linking we can
specify them as normal dependencies.

They are not published yet

No longer needed