In continuation of #70175. There a few things I'd want to sort out before we can recommend people switching to vscode-test and @types/vscode

Already done:

• Published @types/vscode: 1.14 - 1.32
• https://github.com/microsoft/vscode-test
• https://github.com/octref/vscode-test-sample, with Travis and DevOps configurations

For @types/vscode

• Write an Azure function that automates the publishing of @types/vscode when pushing tag to vscode release branch.
• Update samples https://github.com/Microsoft/vscode-extension-samples
• Provide a module vscode-dts, so we can run npx vscode-dts dev or npx vscode-dts 1.30 etc for testing: https://github.com/microsoft/vscode-dts
• vsce for validating @types/vscode versions against engines.vscode: Check @types/vscode version against engines.vscode vscode-vsce#354

For vscode-test:

• Remove lib/shared and update install script Remove lib/shared and update install script vscode-extension-vscode#154
• Move test runner to vscode-test Move test runner to vscode-test vscode-extension-vscode#157
• Update https://code.visualstudio.com/api/working-with-extensions/testing-extension and https://code.visualstudio.com/api/working-with-extensions/continuous-integration: vscode-test related updates vscode-docs#2695
• Upgrade generator