fix(resolve)!: makes alias type derivation more correct and precise BREAKING

[sverweij]

Description

• takes 'workspaces' field into account when merging package manifests
• same for the 'imports' field
• when determining what kind of an alias a thing is use the parsed tsconfig to determine it
• adds alias-tsconfig-base-url and alias-tsconfig-paths dependency types to distinguish between the two types of aliases one can use within tsconfigs. B.t.w. for both dependency-cruiser will keep emitting the alias and alias-tsconfig dependency types as well - both for convenience and backwards compatibility.

This PR is theoretically 🚨 BREAKING as rules previously defined on aliases, that didn't fire now will because they're now detected correctly.

Motivation and Context

Now we're doing explicit things with workspaces and imports fields we need to have them in merged package manifests as well, so in monorepos we still take them into account. The rewrite of the tsconfig alias detection logic is necessary to ensure we detect tsconfig aliases correctly and more precisely.

Also see #863.

How Has This Been Tested?

• green ci
• additional unit tests
• additional integration test(s)

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 a995d26 and detected 0 issues on this pull request.

View more on Code Climate.