E2E VSCode tests are skipped/disabled

[bd82]

There seems to be multiple issues involved.

1. These tests are consistently failing.
   • Checked on both windows/mac local dev machines.
2. On CircleCI starting VSCode during seems to fail on the 2nd+ suite.

This root cause does not seem to be related to this repo's source code
As there are no failing builds merged to master, nor does checking-out the previous release tag resolve the issue.

There are two factors that may be related.

• The tests run on the latest version of VSCode, so that may have changed.
• The tests run on CircleCI docker images which are also updated automatically.

I am currently disabling some of these tests as I am unable to figure out what is the issue.

[bd82]

The second issue where CircleCI only succeeds in starting VSCode once may not need to be resolved
if we/when we would have a better framework for VSCode testing and will only call runTests once.

• https://github.com/SAP/ui5-language-assistant/blob/master/packages/vscode-ui5-language-assistant/test/run-integration-tests.ts#L17-L22

[bd82]

Now encountering random inconsistent failures with the VSCode tests.
I am leaning towards disabling all these E2E tests, it is not the first time we had stability issues with these.

[petermuessig]

Still valid @bd82 ?

[bd82]

I was not impressed with the TCO of these tests.
Perhaps newer versions of the VSCode E2E testing framework should be evaluated...