[Bug] 404's triggered on extension install

MR: Fix open vsx resource url template (gitlab!183071 - merged)

Description

Identified in this thread:

4. Why does the .../extension URL's fail?

So! This seems like a separate issue, but still relevant, and still important to fix... From Open VSX API docs, there's 2 ways we can request individual blobs from an extension:

  1. /vscode/asset/{namespaceName}/{extensionName}/{version}/{assetType}/** (What we currently use)
  2. /vscode/unpkg/{namespaceName}/{extensionName}/{version}/** (What we used to use).

We moved from the vscode/unpkg route to vscode/asset in this MR because:

  1. It seemed like other consumers of VSCode used this route. Now that I'm looking again, I think most use the vscode/unpkg route (although some use the vscode/asset one).
  2. The vscodevim.vim extension started randomly not working :|

But! It looks like the vscode/unpkg route is working now and this is the one that allows us to request a directory which VSCode tries to do with /extension (see relevant code that tried to look for package.nls.json within the directory).

Screenshot_2025-03-03_at_1.02.50_PM

Acceptance criteria

  • Installing an extension doesn't throw a 404 request.

Implementation plan

Let's update main GitLab project to use https://open-vsx.org/vscode/unpkg/{publisher}/{name}/{version}/{path} which supports requesting directories.