integ/test: --disable-workspace-trust

[JadenSimon]

VS code 1.57 introduced a 'trust' feature that is applied to the current workspace, restricting extension access based on trust level. The insiders build allows individual extensions to have a trust level, by default they are untrusted. Untrusted extensions cannot be activated, thus failing the test. We are not particularly concerned with this functionality in regards to other extensions, so we will just disable it entirely when testing.

We should look into this more for our own extension as far as UX is concerned (what should our extension be capable of given a minimum trust level?)

Refer to this issue: microsoft/vscode#120251

Considerations for the toolkit (to be added to package.json):

capabilities:
	untrustedWorkspaces:
		{ supported: true } |
		{ supported: false, description: string } |
		{ supported: 'limited', description: string, restrictedConfigurations?: string[] }

By default, extensions do not support untrusted workspaces. This seems to be the best option for the toolkit for now. In other words, we do not need to update anything unless we want to add a description string for why we do not support untrusted workspaces.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[JadenSimon]

/runintegrationtests

[JadenSimon]

Failed stable test is unrelated.

[bryceitoc9]

/retrybuilds