feat: set fixed versions for vsix extensions

[svor]

What does this PR do?

• Set fixed versions for vsix extensions that are going to be included into the embedded plugin registry;
• Add a script that can update extensions' versions to the latest compatible from opensx.org
• Add GitHub workflow to check new vsix versions and create a PR if new versions exist

openvsx-sync.json

[
  {
    "id": "donjayamanne.githistory",
    "version": "0.6.20"
  },
  {
    "id": "yzane.markdown-pdf",
    "version": "1.5.0"
  },
  {
    "id": "DavidAnson.vscode-markdownlint",
    "version": "0.54.0"
  },
  {
    "id": "robocorp.robotframework-lsp",
    "version": "1.11.0"
  },
  {
    "id": "shardulm94.trailing-spaces",
    "version": "0.4.1"
  },
  {
    "id": "adamhartford.vscode-base64",
    "version": "0.1.0"
  },
...

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-4116

[svor]

With this PR we are going to set fixed versions for all extensions (currently they are latest versions that are compatible with latest che-code version), they won't be updated automatically unless someone updates them by hands or running update_extensions_versions.sh script. It was done to support our own build of extensions with fixed versions in https://github.com/redhat-developer/devspaces-vscode-extensions/tree/devspaces-3-rhel-8 (to be done by https://issues.redhat.com/browse/CRW-4859).

What it gives:

• We know for sure which version is going to be used in the embedded plugin registry and we will build this version in https://github.com/redhat-developer/devspaces-vscode-extensions/tree/devspaces-3-rhel-8, if it is not possible to build on our side - we can change the version. I'd say it's a positive moment
• When new version of some extension is published on openvsx.org, it won't be used by Dev Spaces automatically. To use it we'd need to update the version in openvsx-sync.json. (It's an additional work and probably we'll have new issues from customers "Update extension X to the latest version")
• When we'll switch to use extensions that are building on our side and don't download vsix from openvsx.org , we'd also need to support the build of this new extension's version in https://github.com/redhat-developer/devspaces-vscode-extensions/tree/devspaces-3-rhel-8.

cc @ibuziuk @SDawley @mkuznyetsov

[ibuziuk]

why 5 ?

[svor]

sometimes it fails to get extension's metadata from the openvsx because the internet is unreliable or problem with the openvsx.org server, here we retry to read it 5 times. If it fails 5 times, the script show an error

[SDawley]

The update script for the devspaces-vscode-extensions half of things will have to be updated so it doesn't run the download_vsix script.

[svor]

The update script for the devspaces-vscode-extensions half of things will have to be updated so it doesn't run the download_vsix script.

yes and we'd need to revisit devspaces-vscode-extensions to add more extensions, because it doesn't have the whole list of embedded extensions at this moment.
For existing extensions in devspaces-vscode-extensions, we need to check if the source code revision provides appropriate extension's version. I didn't find a way how we can reference extension's version declared in openvsx.org and extension's source code with the same version.

[svor]

New GH action was added to check new vsix versions and create a PR if new versions exist. This action should be executed on the 1st day of each month

[svor]

@SDawley could you please have another look at this PR. If there are no concerns I'd like to merge this PR and continue work on https://github.com/redhat-developer/devspaces-vscode-extensions part

[devstudio-release]

Build 3.14 :: pluginregistry_3.x/304: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: sync-to-downstream_3.x/6520: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: get-sources-rhpkg-container-build_3.x/6476: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: push-latest-container-to-quay_3.x/4540: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: get-sources-rhpkg-container-build_3.x/6476:

pluginregistry : 3.x :: Build 60539369 : quay.io/devspaces/pluginregistry-rhel8:3.14-2
SUCCESS; copied to quay; /DS_CI/push-latest-container-to-quay_3.x/4540 triggered

[devstudio-release]

Build 3.14 :: pluginregistry_3.x/304:

Upstream sync done; /DS_CI/sync-to-downstream_3.x/6520 triggered

[devstudio-release]

Build 3.14 :: update-digests_3.x/6349: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: operator-bundle_3.x/2827: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: sync-to-downstream_3.x/6525: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: get-sources-rhpkg-container-build_3.x/6481: Console, Changes, Git Data

[devstudio-release]

Build 3.14 :: get-sources-rhpkg-container-build_3.x/6481:

devspaces-operator-bundle : 3.x :: Failed in 60548450 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay