Using --version-range in projects that do not contain Cargo.lock is annoying

[taiki-e]

Currently, cargo-hack runs cargo metadata before the command is run for the specified version, so the format of Cargo.lock is based on the cargo version in which you ran cargo metadata (if Cargo.lock does not exist).

Specifically, if cargo-hack is run on cargo 1.38+ and --version-range received a version smaller than 1.38 and Cargo.lock does not exist, it will fail to compile because it is incompatible with new lock file formats.
https://github.com/taiki-e/auto_enums/runs/1506269414?check_suite_focus=true

This should be workaround by first generating the lock file using an older cargo, but it should be available without such a hack.