Fix for Maximum call stack size exceeded error

[maartengryp-liantis]

Referencing #13

A "Maximum call stack size exceeded error" can be simulated with a POM file containing a single dependency

<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
<version>2.0.54.Final</version>

--- maven-dependency-plugin:2.8:tree (default-cli) @ bookstore-v3 ---
be.liantis:bookstore-v3:jar:0.0.1-SNAPSHOT
- io.netty:netty-tcnative-boringssl-static:jar:2.0.54.Final:compile
+- io.netty:netty-tcnative-classes:jar:2.0.54.Final:compile
+- io.netty:netty-tcnative-boringssl-static:jar:linux-x86_64:2.0.54.Final:compile
+- io.netty:netty-tcnative-boringssl-static:jar:linux-aarch_64:2.0.54.Final:compile
+- io.netty:netty-tcnative-boringssl-static:jar:osx-x86_64:2.0.54.Final:compile
+- io.netty:netty-tcnative-boringssl-static:jar:osx-aarch_64:2.0.54.Final:compile
- io.netty:netty-tcnative-boringssl-static:jar:windows-x86_64:2.0.54.Final:compile

Transitive dependencies, e.g. netty-tcnative-boringssl-static:jar:linux-x86_64, with a classifier (linux-x86_64) are registered as dependencies with a PackageURL equal to the packageURL of the parent netty-tcnative-boringssl-static. As a result, the recursive 'addTransitiveDeps" function never ends ==> Maximum call stack size exceeded

Can be avoided by checking for an unique dependency namespace or dependency name before adding the actual dependency.... Simple test updated to reflect this special case

[peter-murray]

This was fixed by expanding the support for the Maven coordinate system in to the PackageURLs (type and classifier). Thank you for reporting and the suggested fix.