Improve RESOLVES_TO relationships between external and internal Typescript modules

[JohT]

🚀 Feature

• Link NPM dependencies to their packages if possible. Enhancing the data from jqassistant-npm-plugin, package dependencies are now linked to the package they are declared in (if it exists). This makes it easier to navigate by using (NPM:Dependency)-[:IS_DESCRIBED_IN_NPM_PACKAGE]->(NPM:Package).
• Improve project name to distinguish multiple tsconfigs. A Typescript project can have multiple configuration files for example to treat tests differently. Gathering the name solely from the directory name leads to some TS:Project nodes having the same name. Now, the name of the configuration is appended to the name in parentheses. So you can clearly see if a TS:Project is for example representing the tests.
• 🥳 Improve RESOLVES_TO link from external to internal modules. Now, every method to link external to internal modules is separately listed in the result. The existing methods had been improved. A new method that links them using npm package name (including namespace) is added. Additionally, external dependency file extensions are "normalized" to be able to detect the link between a Typescript declaration d.ts to its counterpart, e.g. .ts and to link transpiled .js files from dist folders to their counterpart.

⚙️ Optimization

• Optimize performance for Typescript code bases. Labelling external Java Types now ignores Typescript nodes.
• Add internal change detection switch for testing & debugging. Now, its easier to internally/manually test and debug Typescript scanning by being also able to switch on/off change detection.
• Detect changes for Typescript scanning for each source directory. For large Typescript projects with many source directories it is beneficial to only rescan those source directoryies that were actually changed instead of rescanning them all in case one of them changes. Therefore, there is now one change detection file per source directory.
• Scan included packages if there is no top-level tsconfig.json. For large monorepos that don't have a top-level tsconfig.json file it is beneficial to scan each contained project instead of the whole monorepo. Otherwise it seems that the jQAssistant Typescript Plugin behaves not as expected in that case (seems to pick just one contained tsconfig).
• Change Typescript scan log color to dark grey. Now, it is easer to see which log entries come from the JQAssistant Typescript Plugin and distinguish them from the logs of the automating script .