run playwright tests with temporary workspaces

[ivy-lmu]

& cleaup

[ivy-cst]

You removed the docker way and do installations again on the build host istelf. I think this is not the way we want to go.
Why did you change that in this way?
What do you think @alexsuter?

[ivy-lmu]

You removed the docker way and do installations again on the build host istelf. I think this is not the way we want to go. Why did you change that in this way? What do you think @alexsuter?

The goal of this PR is that each test has its own isolated ivy project. To achieve this, I need to have the built extension, playwright, openvscode server, node, java and maven in one place. Now that this temporary test workspace is working, possible next steps are to get this running again with Docker and also run the openvsocde intergration on github.

[alexsuter]

This is all what I can say

[ivy-cst]

The goal of this PR is that each test has its own isolated ivy project. To achieve this, I need to have the built extension, playwright, openvscode server, node, java and maven in one place. Now that this temporary test workspace is working, possible next steps are to get this running again with Docker and also run the openvsocde intergration on github.

Ok, why on github?

[ivy-lmu]

The goal of this PR is that each test has its own isolated ivy project. To achieve this, I need to have the built extension, playwright, openvscode server, node, java and maven in one place. Now that this temporary test workspace is working, possible next steps are to get this running again with Docker and also run the openvsocde intergration on github.

Ok, why on github?

because I want to compare with our internal build node 😽

[alexsuter]

💋