Using `git` in Cargo.toml for getting latest commit fails compiling due to non-existing v8 commit

[TimDiekmann]

When using v8 = { git = "https://github.com/denoland/rusty_v8" } in Cargo.toml, cargo is not able to get the git submodule for v8.

This happens, when v8 got updated by @denobot by auto-roll, but rusty_v8's submodule to v8 still points to an old commit. This is likely because @denobot force pushes, so the commit pointed by the submodule, is not tracked in the v8 repository anymore. For example, currently, the submodule is pointing to b11f2083fb71814a31cbb79ca600fbc153e77db7, this will result in:

Execution failed (exit code 101).
/home/***/.cargo/bin/cargo metadata --verbose --format-version 1 --all-features
stdout :     Blocking waiting for file lock on package cache
    Updating git repository `https://github.com/denoland/rusty_v8`
    Updating git submodule `https://github.com/denoland/v8.git`
error: failed to get `v8` as a dependency of package `v8-test v0.1.0 (/home/***/v8-test)`

Caused by:
  failed to load source for dependency `v8`

Caused by:
  Unable to update https://github.com/denoland/rusty_v8

Caused by:
  failed to update submodule `v8`

Caused by:
  object not found - no match for id (b11f2083fb71814a31cbb79ca600fbc153e77db7); class=Odb (9); code=NotFound (-3)

stderr :