[MENFORCER-494] Allow banning dynamic versions in whole tree

[JimmyAx]

This commit introduces the possibility of banning dynamic versions in the entire dependency tree before Maven computes the final dependency tree. If a dependency exists multiple times in the dependency tree the plugin will not detect any dynamic versions as long as the final dependency tree does not have any dynamic versions.

In this example the dependency A -> C -> D is not detected with a dynamic version unless the verbose parameter has been set in this pull request.

A
+- B
|  \- D version 1.0
\- C
   \- D version [1.0,2.0)

Following this checklist to help us incorporate your contribution quickly and easily:

• [X] Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
• [X] Each commit in the pull request should have a meaningful subject line and body.
• [X] Format the pull request title like [MENFORCER-XXX] - Fixes bug in ApproximateQuantiles, where you replace MENFORCER-XXX with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message.
• [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• [X] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
• [X] You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement if you are unsure please ask on the developers list.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004 you have to acknowledge this by using the following check-box.

• [X] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• [x] In any other case, please file an Apache Individual Contributor License Agreement.