Support for --explicit-version in cargo vendor

[acmcarther]

As requested by the embedded error message on flag usage, I'm filing this bug to request re-inclusion of versioning functionality.

I maintain cargo-raze, a tool that generates BUILD files for Cargo dependencies for projects using the Bazel build tool. Historically the cargo-vendor crate has been a primary component of our "pre vendored dependency" use case, and we rely on explicitly versioned crate directory output in order to make the generated output directories more predictable.

Without this functionality, we'll need to suggest users continue to use the cargo-vendor crate, deprecate the vendored dependency use case, or package this functionality into our own crate.

[apoelstra]

Is there any way to update the toolchain past 1.36 with this bug present?

[apoelstra]

Ah! Directly calling cargo-vendor vendor (two vendors) is the workaround.

[jgallagher]

Is this resolved as of #7631? (Sorry if this is an out-of-left-field comment, but I was just poking around and noticed that cargo-raze as linked in the original request had updated its Readme to reference the new --versioned-dirs flag added in that PR.)

[ehuss]

Yes, this appears to be done, thanks!