[MENFORCER-455] New Enforcer API

[slawekjaranowski]

• New API based on JSR 330 components

---

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

• 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.
• Each commit in the pull request should have a meaningful subject line and body.
• 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.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• 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.

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

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

[slawekjaranowski]

TODO:

• documentation for new API
• move Built-In Rules to new API - can be done in separate PR

[kwin]

Hm, this is really legacy. New code should no longer rely on that but rather on https://www.eclipse.org/sisu/docs/api/org.eclipse.sisu.inject/reference/org/eclipse/sisu/inject/BeanLocator.html for dynamic lookup

[kwin]

We shouldn't support custom rules with legacy plexus annotations at all but only ones leveraging JSR 330 annotations.

[slawekjaranowski]

So which Maven component should we use for lookup only JSR 330?

[slawekjaranowski]

Even in new Api we use PlexusContainer

https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/internal/impl/DefaultLookup.java

So now I don't see another way.

[slawekjaranowski]

@kwin Do you accept my responses?
Can I do anything more with this PR?

Anybody else has any more remarks?
I would like to merge and go forward.

[kwin]

LGTM