feat(extract): makes support for workspaces explicit

[sverweij]

Description

• adds explicit detection of modules aliased via workspaces
• introduces the aliased-workspace dependency type

Motivation and Context

Imports from workspaces have been well-supported in dependency-cruiser since the stone age. Not by briliant foresight, but because it plugs into the regular node.js module resolution - workspaces are symlinks in node_modules sorta automatically linked to local folders. Dependency-cruiser didn't explicitly name them as separate dependency-types (instead slotting them into dependency type 'local' or 'npm-no-pkg' (when npm i wasn't run on the folder yet)). This PR corrects that oversight.

This PR also fixes a bug uncovered by @throrin19: workspace imports were erroneously classified as tsconfig aliases (see #863 for details).

How Has This Been Tested?

• green ci
• additional unit tests
• additional integration test

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Documentation only change
• Refactor (non-breaking change which fixes an issue without changing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• 📖

  • My change doesn't require a documentation update, or ...
  • it does and I have updated it

• ⚖️

  • The contribution will be subject to The MIT license, and I'm OK with that.
  • The contribution is my own original work.
  • I am ok with the stuff in CONTRIBUTING.md.

[codeclimate]

Code Climate has analyzed commit aa2860f and detected 0 issues on this pull request.

View more on Code Climate.