Locking to non-existing rev in git dependency lockfile will result in cannot find package error from the resolver

[maciektr]

Problem

The resolver should be able to ignore locks pointing to non-existing revs.

Steps

1. Add a git dependency and run Scarb build. The lockfile should be produced, pointing to specific commit hash.
2. Remove this commit hash from remote repository (with force push or smth).
3. Try do build the package once again without removing the lockfile.
4. Package will fail to build with cannot find package error from resolver

Possible Solution(s)

No response

Notes

No response

Version

No response