e2e Test: Test complicated environment setups

[jonvanausdeln]

There have been a few issues with more complicated user environments. This often is the case on workbench, but can happen on desktop as well. For example, there was a recent regression where .venv in a workspace was not being started automatically.

The thought is to create a separate workflow that has more complicated setup. This would run perhaps nightly? The reason for the separate workflow is to avoid the need for the complicated setup in the "normal" testing, both local and in CI.

Things that it might include:

• Several different types of python virtual environments
• Unusual install locations for both R & Python
• Unsupported versions of R & Python

We could also then move the "include" tests of interpreters to this workflow and remove that part of the setup from the other CI workflows

Some things to consider

• Need to exclude these tests from other workflows
• Perhaps could add the ability to specify the working directory of the test, e.g where qa-example-repo gets cloned into.
• Could this be helped with docker container work?