Feature Request: Support non-standard tarball urls in JFrog Artifactory

[banyudu]

In JFrog Artifactory based npm registry, tarball urls are not always:

${registry}${pkgName}/-/${scopelessName}-${removeBuildMetadataFromVersion(pkgVersion)}.tgz

There are two different cases for scoped packages:

1. Synced npm packages, such as @pnpm/[email protected], resolves to http://myhost/artifactory/api/npm/npm-virtual/@pnpm/exe/-/exe-7.18.2.tgz
2. Self Managed packages, say @mycompany/[email protected], resolves to http://myhost/artifactory/api/npm/npm-virtual/@mycompany/sth/-/@mycompany/sth-1.0.0.tgz, which uses full name instead of scopeless name.

This issue makes a lot confusion when we trying to migrate to pnpm, and the best solution so far is enable lockfile-include-tarball-url.

Could there be an option to use full name instead of scopeless name for given scopes?