[INTERNAL] Print error cause stack trace

This improves error analysis as the FileLinter catches errors and
re-throws them with the original error as "cause". However, this
information is missing when printed to the console output so often it
is not clear where an exception originates from.

Author: matz3

packages/ui5-linter/src/cli/base.ts

@@ -141,6 +141,11 @@ export default function base(cli: yargs.Argv) {
 							process.stderr.write(err.stack + "\n");
 							process.stderr.write("\n");
 						}
+						if (err.cause instanceof Error && err.cause.stack) {
+							process.stderr.write(chalk.underline("Error Cause Stack Trace:\n"));
+							process.stderr.write(err.cause.stack + "\n");
+							process.stderr.write("\n");
+						}
 						process.stderr.write(
 							chalk.dim(
 								`If you think this is an issue of the ui5-linter, you might report it using the ` +