fix(upgrade): Fix yarn upgrade when using --scope with exotic deps

[rally25rs]

Summary

Exotic dependencies (github urls for example) were not being unlocked from the lockfile when running
yarn upgrade --scope @whatever/ which was resulting in dependencies not being upgraded. This was
due to trying to find the dep in the lockfile just by it's url instead of in name@url format.

For example if you have the dependency:

    "@yarn/test-git-repo": "https://github.com/yarnpkg/e2e-test-repo#master"

then yarn.lock contains

"@yarn/test-git-repo@https://github.com/yarnpkg/e2e-test-repo#master":
  version "1.0.0"
  resolved "https://github.com/yarnpkg/e2e-test-repo#5c57959f3c55a6cd6004e3855ca59ba98bfff56c"

but when yarn upgrade would try to unlock the dependency, it was searching for a lock on

https://github.com/yarnpkg/e2e-test-repo#master

instead of on

@yarn/test-git-repo@https://github.com/yarnpkg/e2e-test-repo#master

This resulted in the dependency still being locked to the previous version/SHA and no upgrade being performed.

fixes #7016

Test plan

Added regression test for scoped github dependency. (fixtures/upgrade/package-not-in-registry-scoped)

Also fixed an existing test; __tests__/fixtures/upgrade/package-not-in-registry/yarn.lock already had the latest commit sha in the lockfile, so the upgrade that it was testing never actually had to change versions, it was already current. I changed the sha in the lockfile to an older commit so that the upgrade would actually have to do something for the test to pass.

[marcoadkins]

Good catch 👍