* <p>
 * This interface serves as the base for all Service Provider Interface (SPI) components in Maven.
 * Classes implementing this interface can be discovered and loaded by Maven through the
 * Java ServiceLoader mechanism, allowing plugins and extensions to contribute functionality
 * to the Maven build process.
 * <p>

 * beyond the standard ones provided by Maven (like clean, default, site). Lifecycles define a sequence
 * of phases that can be executed during a build.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and their provided lifecycles will be available throughout the Maven build process.
 * <p>
 * Example usage:
 * <pre>

 * beyond the standard ones provided by Maven. Path scopes define how dependencies are used
 * in different contexts, such as compilation, testing, or runtime.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and their provided path scopes will be available throughout the Maven build process.
 * <p>
 * Example usage:
 * <pre>

 * beyond the standard ones provided by Maven (like jar, war, pom, etc.). Types define how artifacts
 * are handled, including their default extension, classifier, and language.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and their provided types will be available throughout the Maven build process.
 * <p>
 * Example usage:
 * <pre>
 * public class CustomTypeProvider implements TypeProvider {

 * to various categories like languages, scopes, and packaging types. This interface is the
 * base for all providers that register such extensions.
 * <p>
 * Implementations of this interface are discovered through the Java ServiceLoader mechanism.
 * Each implementation must be registered in a {@code META-INF/services/} file corresponding
 * to the specific provider interface being implemented.
 * <p>

 *   <li>Effective model - The fully processed model with all interpolation and inheritance applied</li>
 * </ol>
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and will be called in sequence during model building.
 * <p>
 * Example usage:
 * <pre>
 * public class CustomModelTransformer implements ModelTransformer {

 * <p>
 * This interface allows plugins and extensions to define and register additional programming languages
 * beyond the standard ones provided by Maven. Implementations of this interface will be discovered
 * through the Java ServiceLoader mechanism and their provided languages will be available
 * throughout the Maven build process.
 * <p>
 * Example usage:
 * <pre>

    @Nonnull
    default Optional<OutputStream> stdErr() {
        return Optional.ofNullable(parserRequest().stdErr());
    }

    /**
     * Returns a list of core extensions from all sources, that were discovered and loaded. Each instance of
     * {@link CoreExtensions} is validated, but the list elements may have overlapping elements, that requires
     * some logic to sort out (like precedence).
     * <p>

            return List.of();
        }

        return selectCoreExtensions(
                context, context.invokerRequest.coreExtensions().orElseThrow());
    }

    /**
     * Selects extensions to load discovered from various sources by precedence ("first wins"), as
     * {@link InvokerRequest#coreExtensions()} is in precedence order. Also reports conflicts, if any.
     * Finally, at DEBUG level reports configured vs selected extensions.

 *   <li>Intern objects for faster equality comparisons</li>
 *   <li>Apply custom optimization strategies</li>
 *   <li>Transform or modify objects during building</li>
 * </ul>
 *
 * <p>Implementations are discovered via the Java ServiceLoader mechanism and should
 * be registered in {@code META-INF/services/org.apache.maven.api.model.ModelObjectProcessor}.</p>
 *
 * <p>The service is called during model building for all model objects, allowing