Offline mirror collision with npm aliased package name

[slimreaper35]

Related to: #634

We added this check to prevent tarballs in the cache from being overwritten. For example, there is a registry package and a URL package that share the identical tarball name.

The problem is when a dependency uses an alias, which apparently leads yarn to create duplicate records inside yarn.lock if that dependency is already required. Cachi2 "detects" this collision and refuses to proceed with the request.

Example of npm aliases:

"@isaacs/cliui@^8.0.2":
  version "8.0.2"
  resolved "https://registry.yarnpkg.com/@isaacs/cliui/-/cliui-8.0.2.tgz#b37667b7bc181c168782259bab42474fbf52b550"
  integrity sha512-O8jcjabXaleOG9DQ0+ARXWZBTfnP4WNAqzuiJK7ll44AmxGKv/J2M4TPjxjY3znBCfvBXFzucm1twdyFybFqEA==
  dependencies:
    string-width "^5.1.2"
    string-width-cjs "npm:string-width@^4.2.0"
    strip-ansi "^7.0.1"
    strip-ansi-cjs "npm:strip-ansi@^6.0.1"
    wrap-ansi "^8.1.0"
    wrap-ansi-cjs "npm:wrap-ansi@^7.0.0"

To reproduce this behavior:

git clone git@github.com:kiali/kiali.git
cd kiali
git switch v2.2
cd frontend
cachi2 fetch-deps yarn

One of multiple dependencies that are present twice in the yarn.lock:

wrap-ansi@^7.0.0
npm alias - https://github.com/kiali/kiali/blob/v2.2/frontend/yarn.lock#L13533
yarn - https://github.com/kiali/kiali/blob/v2.2/frontend/yarn.lock#L13551