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.

I couldn't find any breaking changes affecting us

They are not published yet

karma-chrome-launcher doesn't support newer chrome yet

Use code splitting instead

also provies a function for css content icons (a bit hacky as it uses masks)

This uses sentry internally, but only sends things to the server when
configured that way.

So that packages depending on it install it as well

node-resolve wasn't limited to the local node_modules and picked up the
dependency from another package on my machine.

When specifying a package for code splitting, rollup requires the
packages to have a valid entry point for some reason.

Add an empty one.