Improve useability

[JohT]

🚀 Feature

• Auto detect neo4j directory to start/stop a not yet updated version. If your local analysis workspace uses an older version of Neo4j, you can now use commands like startNeo4j.sh and stopNeo4j.sh without the need to install the newest Neo4j and run the local analysis all over again.
• Add custom hashfile path option to change detection.
• Scan Typescript sources only on changes. If you want to analyze lots of Typescript projects, scanning can take some time. If there are no changes, a rescan isn't necessary and won't be done anymore. This is helpful when working locally.
• Add further Axon Framework artifacts to analyze.

⚙️ Optimization

• Ignore .DS_Store files while scanning.
• Delete plain files in .git directory since they can't be ignored for. All jQAssistant plugins are called to analyze a given path. By specifying a .git directory, this would lead to not only importing the git data, but also all the plain metadata files, that aren't typically wanted. As long as this isn't configurable (see Config property jqassistant.scan.include.files should support file patterns (e.g. wild cards) jQAssistant/jqassistant#410)) they will be deleted after scanning.
• Improve performance by only searching relevant paths. Now, folders like node_modules won't be searched anymore for Typescript analysis files or .git directories to analyze, which makes the search faster.
• Add progress and improve performance of change detection. Now, change detection for files runs faster and provides a progress output in the console.
• Copy Typescript scanning log to console and file. Now, the progress of the Typescript scan is shown again in the console and additionally copied into a log file.
• Rename to more general detectChangedFiles. Now, change detection is also used for analyzing Typescript projects and needs to be more general. Therefore, it can not only be used to detect changes in the artifacts directory, but also in the source directory or other cases.
• Remove ts-lce patch from commit 291bcec. This workaround is no longer needed.

🛠 Fix

• Fix git file matching ambiguity for multi repository analysis. Files that appear in multiple sources like e.g. package.json should be linked to the according git repository leading to unambiguously resolved git to code files.
• Resolve external modules to internal when file extensions match. If one Typescript project uses an external module and another one provides that as an internal module, a RESOLVES_TO relationship will be created. Now, this relationship will only be created when the module extensions match so that e.g. different files like images.json and images.ts won't be linked together.
• Add data verification before projection creation.. Previously, algorithms like Leiden Community Detection would have failed with wired error messages like the return value of "org.neo4j.gds.leiden.LeidenResult.dendrogramManager()" is null. Now, there is a verification query before data is projected for algorithms. If node or relationship properties are missing, the query will output what is missing, how often the case appeared and will then fail with a more expressive error message.
• Fix low coupling weight = 0 on when there are no declarations.
• Fix missing runtime logs directory on Windows