Build a CompilerManager through ServiceLoader

[slachiewicz]

DefaultCompilerManager.fromServiceLoader(ClassLoader) builds a compiler manager from META-INF/services instead of a Sisu container, so a plugin written to the Maven 4 API, which cannot inject Sisu components from its own jars, can create one and bind it with a @Provides method. The Sisu wiring is unchanged.

Compilers are keyed by their @Named value, as Sisu does. @Singleton compilers (javac, eclipse) are shared; aspectj, csharp and javac-errorprone get a new instance per getCompiler call, as with Sisu. A provider that cannot be loaded is skipped with a warning. Two small changes make the compilers load without a container: JavacCompiler creates its JavaxToolsCompiler when nothing injects one, and AbstractCompiler creates its deprecated Plexus logger wrapper on first use, because the Plexus logging API is only provided by Maven at run time.

The new plexus-compiler-service-loader-test module checks that each compiler module's services file lists the same classes as its generated Sisu index.

Same approach as apache/maven-scm#1418; context in apache/maven#13302.

Verified: mvn verify → full reactor green, 12 ITs; 5 new tests.

[slachiewicz]

Not needed: Maven 4 API mojos will inject Sisu components from their plugin realm through javax.inject (apache/maven#13326), so the Maven 4 port injects this manager as on Maven 3. Tracked in apache/maven#13309.