Run e2e tests in docker

[nicodh]

Reduced Dockerfile

Use only Chrome as playwright project to reduce test duration:

• webkit does not yet support clipboard access in playwright
• firefox will probably never be used (in tauri)

[Simon-Laux]

webkit does not yet support clipboard access in playwright

you could also do:

• ignore clipboard dependent tests on webkit but run the other tests
• provide a different runtime while the browser version is in testing -> a testing runtime.js that mocks the clipboard access (and let's you control it from playwright)

[WofWca]

I can see that this now doesn't override node_modules. Very nice. But still, what files does this write? Why do we need this? Is this the HTML report file that Playwright generates? Wouldn't it be better to keep it in the container instead of writing to host? Using the outputFolder option.