question: should the search response include the downloadUrl as part of 'allVersions'

[vince-fugnitto]

Description

The search API response now includes an updated allVersions object which contains information regarding all versions of an extension and their corresponding engines fields. I noticed that part of this object we include the url which points to the api but I was wondering should we not instead/or in addition to include the download url? Is the idea that clients will need to perform an additional request to obtain the proper download url once they determine a compatible extension? Perhaps it'd be more useful to include the download url instead so this extra request is not necessary.

For example: https://open-vsx.org/api/-/search?query=prettier

"allVersions":[
  {
    "url":"https://open-vsx.org/api/esbenp/prettier-vscode/5.1.3",
    "version":"5.1.3",
    "engines":{
      "vscode":"^1.41.0"
    }
  },
  {
    "url":"https://open-vsx.org/api/esbenp/prettier-vscode/5.1.0",
    "version":"5.1.0",
     "engines":{
       "vscode":"^1.41.0"
     }
  }
]

[spoenemann]

We can add the download URL in addition to the metadata URL.