remotes:::download_version_url assumes that packages in src/contrib/Archive are organized in a flat manner (like on CRAN). Artifactory, however, seems to organize archived packages by having intermediate version folders like src/contrib/Archive/<package_name>/<version>/<package_name>_<version>.tar.gz.

It seems like the package path assumptions could be relaxed to support both models.