Cyclic Dependency when project depends on itself

[knrc]

Maven normally excludes cyclic dependencies, however there is one case when this is allowed. This results in recursion leading to a StackOverflowError.

This was first discovered when generating a bom for the netty-tcnative project which includes netty-tcnative-boringssl-static.
The netty-tcnative-boringssl-static project has dependencies on itself, albeit with individual qualifiers (such as linux-x86_64) for each of its supported binaries.

[knrc]

The submitted PR includes a test case which results in the following dependency tree

com.example.cyclic:cyclic_A:jar:1.0.0
+- com.example.cyclic:cyclic_A:jar:classifier_1:1.0.0:compile
|  +- (com.example.cyclic:cyclic_A:jar:classifier_2:1.0.0:compile - omitted for duplicate)
|  \- (com.example.cyclic:cyclic_A:jar:classifier_3:1.0.0:compile - omitted for duplicate)
+- com.example.cyclic:cyclic_A:jar:classifier_2:1.0.0:compile
|  +- (com.example.cyclic:cyclic_A:jar:classifier_1:1.0.0:compile - omitted for duplicate)
|  \- (com.example.cyclic:cyclic_A:jar:classifier_3:1.0.0:compile - omitted for duplicate)
\- com.example.cyclic:cyclic_A:jar:classifier_3:1.0.0:compile
   +- (com.example.cyclic:cyclic_A:jar:classifier_1:1.0.0:compile - omitted for duplicate)
   \- (com.example.cyclic:cyclic_A:jar:classifier_2:1.0.0:compile - omitted for duplicate)