Ability to block extensions installation via CLI and VSIX

[RomanNikitenko]

Depends on: #605

What does this PR do?

• Moves default extensions functionality from the che-extension to the VS Code side
• this ^ is required to fix https://issues.redhat.com/browse/CRW-9626
• adds ability to block extensions installation using CLI: vscode-editor-configurations ConfigMap => policy.json section => BlockCliExtensionsInstallation property
• adds ability to block extensions installation using workbench.extensions.command.installFromVSIX API command: vscode-editor-configurations ConfigMap => policy.json section => BlockInstallFromVSIXCommandExtensionsInstallation property
• adds ability to block default extensions installation: vscode-editor-configurations ConfigMap => policy.json section => BlockDefaultExtensionsInstallation property

What issues does this PR fix?

• https://issues.redhat.com/browse/CRW-9626
• https://issues.redhat.com/browse/CRW-8866

How to test this PR?

Prerequisites

Add default-extensions ConfigMap to your namespace:

default-extensions ConfigMap

kind: ConfigMap
apiVersion: v1
metadata:
  name: default-extensions
  labels:
    controller.devfile.io/mount-to-devworkspace: 'true'
    controller.devfile.io/watch-configmap: 'true'
  annotations:
    controller.devfile.io/mount-as: env
data:
  DEFAULT_EXTENSIONS: '/tmp/atlassian.atlascode-3.0.10.vsix;/tmp/snowflake.snowflake-vsc-1.9.1.vsix'

Add vscode-editor-configurations ConfigMap to your namespace:

vscode-editor-configurations ConfigMap

kind: ConfigMap
apiVersion: v1
metadata:
  name: vscode-editor-configurations
  namespace: eclipse-che
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: workspaces-config
data:
  configurations.json: |
    {
      "extensions.install-from-vsix-enabled": false
    }

Use Cases:

1. Default extensions should be installed when "Install from VSIX" is disabled (fix for `CRW-9626`)

• start workspace: click here
• open a terminal, run: /checode/checode-linux-libc/ubi9/bin/remote-cli/code-oss --install-extension /projects/web-nodejs-sample/redhat.java-1.43.1.vsix
• open a terminal, run: /checode/checode-linux-libc/ubi9/bin/remote-cli/code-oss --install-extension /projects/web-nodejs-sample/vscode-test-extension-0.0.1.vsix
• F1 => Test 'installFromVSIX'

Expected behavior:

• Extensions panel => ... => Install from VSIX action is absent
• Extensions panel => Atlassian, Snowflake and YAML extensions are installed as default extensions
• Language Support for Java extension is installed using CLI
• Tools for MicroProfile extension is installed using 'workbench.extensions.command.installFromVSIX API command

2. Default extensions should be installed, but installation using CLI should be blocked

• add the following section to the vscode-editor-configurations ConfigMap

policy.json: |
    {
      "BlockCliExtensionsInstallation": true      
    }

• delete previous workspace
• start a new workspace: click here
• open a terminal, run: /checode/checode-linux-libc/ubi9/bin/remote-cli/code-oss --install-extension /projects/web-nodejs-sample/redhat.java-1.43.1.vsix

Expected behavior:

• Extensions panel => ... => Install from VSIX action is absent
• Extensions panel => Atlassian, Snowflake and YAML extensions are installed as default extensions
• Language Support for Java extension installation was failed using CLI

3. Default extensions should be installed, but installation using workbench.extensions.command.installFromVSIX API command should be blocked

• replace the following section in the vscode-editor-configurations ConfigMap

policy.json: |
    {
      "BlockInstallFromVSIXCommandExtensionsInstallation": true      
    }

• delete previous workspace
• start a new workspace: click here
• open a terminal, run: /checode/checode-linux-libc/ubi9/bin/remote-cli/code-oss --install-extension /projects/web-nodejs-sample/vscode-test-extension-0.0.1.vsix
• F1 => Test 'installFromVSIX'

Expected behavior:

• Extensions panel => ... => Install from VSIX action is absent
• Extensions panel => Atlassian, Snowflake and YAML extensions are installed as default extensions
• Tools for MicroProfile extension installation was failed using 'workbench.extensions.command.installFromVSIX API command

4. Default extensions installation should be blocked

• replace the following section in the vscode-editor-configurations ConfigMap

policy.json: |
    {
      "BlockDefaultExtensionsInstallation": true
    }

• delete previous workspace
• start a new workspace: click here

Expected behavior:

• Extensions panel => ... => Install from VSIX action is absent
• Extensions panel => Atlassian, Snowflake and YAML extensions are NOT installed as default extensions

Does this PR contain changes that override default upstream Code-OSS behavior?

• the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
• the corresponding items were added to the CHANGELOG.md file
• rules for automatic git rebase were added to the .rebase folder

[github-actions]

Click here to review and test in web IDE:

[github-actions]

Pull Request images published ✨

Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-617-amd64
Editor arm64: quay.io/che-incubator-pull-requests/che-code:pr-617-arm64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-617-dev-amd64

[github-actions]

Pull Request images published ✨

Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-617-amd64
Editor arm64: quay.io/che-incubator-pull-requests/che-code:pr-617-arm64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-617-dev-amd64

[github-actions]

Pull Request images published ✨

Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-617-amd64
Editor arm64: quay.io/che-incubator-pull-requests/che-code:pr-617-arm64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-617-dev-amd64