[MENFORCER-519] "BannedPluginDependencies" Rule

**[Jacques Burns](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jmathewburns)** opened **[MENFORCER-519](https://issues.apache.org/jira/browse/MENFORCER-519?redirect=false)** and commented

We ran into this issue at work where we had to prevent a certain JAR from ever appearing in the local repository of our build server. I was thinking of solving this with the Enforcer plugin, but it turns out that the JAR is also a dependency of some of the Maven plugins we use, and the Enforcer plugin doesn't check that. I realise it could probably be a custom rule, but maybe there could be a general desire for that kind of functionality.

I'm willing to do the work on this and submit the PR, but first, is it something you folks would like added?

---
No further details from [MENFORCER-519](https://issues.apache.org/jira/browse/MENFORCER-519?redirect=false)

The issue names no files, tests, or entry points. Start by clarifying whether the proposed rule should inspect Maven plugin dependencies as well as project dependencies, then review how the Enforcer plugin currently checks dependencies. Done means defining the rule's scope and behavior well enough to implement and test it.

Written by the indexing model from the issue text.