fix(ls): correctly show deduped dependencies

[milaninfy]

Attempt to fix npm ls output

Problem:

• deduped nodes are cloned when encountered using previously seen nodes set but they are not explored further when we are requesting npm ls dep-name if dep-name is a child of some deduped parent then whole tree would be shown till that parent but logically dep-name is still the child/grand-child of that.
• When deduped nodes are explored further it results in cycle when dep1 is ancestor of dep2 which again depends on dep1 creating a cycle when explored, also the algorithm used is BFS so it's hard to detect cycle.

Solution:

• Use DFS like approach with custom cycle detection checks.
  • keep track of how any node is discovered. so each node or parent node will have a list containing all the relevant visited nodes, we check if current node is in that list then it's a cycle and we don't need to explore this node.
• This solution attempts to explore cloned nodes of deduped nodes and use cached result so that it fixes the output and perform better. since those nodes are deduped and already explored we can use the result.

Progress:

• still some cases which might result in Infinite loop and need to discovered those.
• very slow and uses very large memory during run when ran on big repo, need to find out optimizations or better approach
• Fix/add the test cases
• Refactor

Test output

`npm ls child` - before and after

~/workarea/rep/repro $ npm ls child
repro@1.0.0 /Users/milaninfy/workarea/rep/repro
└─┬ relative-p2@1.0.0
  └─┬ grand-p1@1.0.0
    └─┬ parent-p1@1.0.0
      └── child@1.0.0

~/workarea/rep/repro $ lnpm ls child
repro@1.0.0 /Users/milaninfy/workarea/rep/repro
├─┬ relative-p1@1.0.0
│ └─┬ family@1.0.0
│   └─┬ grand-p1@1.0.0
│     └─┬ parent-p1@1.0.0
│       └── child@1.0.0
└─┬ relative-p2@1.0.0
  └─┬ grand-p1@1.0.0 deduped
    └─┬ parent-p1@1.0.0 deduped
      └── child@1.0.0 deduped

fixes: #7917

[wraithgar]

This is displaying root nodes which are explicitly there cause of being a dependency as deduped which seems like an overstep.

deduped

The base npm ls should be much smaller than this PR makes it. For example with npm itself arborist has the mock registry fully listed in it instead of deduped.

this PR:

├─┬ @npmcli/arborist@9.1.4 -> ./workspaces/arborist
│ ├── @isaacs/string-locale-compare@1.1.0 deduped
│ ├── @npmcli/eslint-config@5.1.0 deduped
│ ├── @npmcli/fs@4.0.0
│ ├── @npmcli/installed-package-contents@3.0.0
│ ├── @npmcli/map-workspaces@4.0.2
│ ├── @npmcli/metavuln-calculator@9.0.1
│ ├─┬ @npmcli/mock-registry@1.0.0 -> ./mock-registry
│ │ ├── @npmcli/arborist@9.1.4 deduped -> ./workspaces/arborist
│ │ ├── @npmcli/eslint-config@5.1.0 deduped
│ │ ├── @npmcli/template-oss@4.24.4
│ │ ├── json-stringify-safe@5.0.1
│ │ ├── nock@13.5.6
│ │ ├── npm-package-arg@12.0.2
│ │ ├── pacote@21.0.0
│ │ └── tap@16.3.10

npm:

├─┬ @npmcli/arborist@9.1.4 -> ./workspaces/arborist
│ ├── @isaacs/string-locale-compare@1.1.0 deduped
│ ├── @npmcli/eslint-config@5.1.0 deduped
│ ├── @npmcli/fs@4.0.0 deduped
│ ├── @npmcli/installed-package-contents@3.0.0
│ ├── @npmcli/map-workspaces@4.0.2 deduped
│ ├── @npmcli/metavuln-calculator@9.0.1
│ ├── @npmcli/mock-registry@1.0.0 deduped -> ./mock-registry

Later, mock-registry (which is a root node) is also shown in both, but this PR dives back into arborist, and itself.

this PR:

├─┬ @npmcli/mock-registry@1.0.0 deduped -> ./mock-registry
│ ├─┬ @npmcli/arborist@9.1.4 -> ./workspaces/arborist
│ │ ├── @isaacs/string-locale-compare@1.1.0 deduped
│ │ ├── @npmcli/eslint-config@5.1.0 deduped
│ │ ├── @npmcli/fs@4.0.0
│ │ ├── @npmcli/installed-package-contents@3.0.0
│ │ ├── @npmcli/map-workspaces@4.0.2
│ │ ├── @npmcli/metavuln-calculator@9.0.1
│ │ ├─┬ @npmcli/mock-registry@1.0.0 -> ./mock-registry
│ │ │ ├── @npmcli/arborist@9.1.4 deduped -> ./workspaces/arborist
│ │ │ ├── @npmcli/eslint-config@5.1.0 deduped
│ │ │ ├── @npmcli/template-oss@4.24.4
│ │ │ ├── json-stringify-safe@5.0.1
│ │ │ ├── nock@13.5.6
│ │ │ ├── npm-package-arg@12.0.2
│ │ │ ├── pacote@21.0.0
│ │ │ └── tap@16.3.10

npm:

├─┬ @npmcli/mock-registry@1.0.0 -> ./mock-registry
│ ├── @npmcli/arborist@9.1.4 deduped -> ./workspaces/arborist
│ ├── @npmcli/eslint-config@5.1.0 deduped
│ ├── @npmcli/template-oss@4.24.4 deduped
│ ├── json-stringify-safe@5.0.1
│ ├── nock@13.5.6 deduped
│ ├── npm-package-arg@12.0.2 deduped
│ ├── pacote@21.0.0 deduped
│ └── tap@16.3.10 deduped

As it is I don't thing this fix is right. The base npm ls is mostly correct already and doesn't need to spool out like this. I do know there are cases where deduped nodes are displayed in the base npm ls but not later shown in their actual location, which would be a bug to fix. There is also the core bug listed when doing npm ls <dep>