Problem

When deploying a crate with a registry dependency, the client tries to resolve the dependency from the specified URL.
In JFrog we want to support cargo sparse index for a virtual repository as well - which means that we are resolving files without really knowing their source.
The problem is that the client will fetch the dependencies from the real source, instead of the registry in the config.toml file.
In order to resolve this issue we need the option to tell the cargo client to replace any source (maybe [source.any]), and not only specific sources like [source.crates-io]

Proposed Solution

Provide another known source that will be relevant for any source. or an option to direct all cargo requests to a specific registry (including URLs of dependencies)

Notes

No response