Consider addressing stable version of VS Code + Extensions

[gbroques]

Should we try and address or centralize the version of VS Code and extensions developers use?

Occasionally we may have to deal with issues because the latest version of VS Code or version of an extension breaks something or causes unexpected or undesirable results.

Versions of VS Code can be found at:
https://code.visualstudio.com/updates/

Releases of extensions can be found at their releases page on GitHub and the corresponding .vsix file downloaded:
https://github.com/microsoft/vscode-python/releases/tag/2020.7.96456
https://github.com/microsoft/vscode-python/releases/download/2020.7.96456/ms-python-release.vsix

We can also use the CLI:
code --install-extension <extension-id[@version]

For example, code --install-extension ms-python.python@2020.7.96456.

My gut tells me which should extend the editor-config command and break it apart.

For example:

• osewb editor extension install
• osewb editor extension update
• osewb editor config
• osewb editor install
• osewb editor update

We then control what version of VS Code to use in the platform.

However, this will be a pain to keep up to date because there are frequent releases (monthly for VS Code) and frequent enough releases for extensions.

Still, we should be able to transmit and share what unique set of versions of VS Code + extensions are known to work with a particular version of OSE Workbench Platform.

[gbroques]

I don't like giving OSE Workbench Platform good reason to change frequently.

Maybe tight integration with an editor is too much responsibility and can be delegated to a "editor provider" package that OSE Workbench Platform integrates with.