Delaying execution to the end of multi-module project with Maven parallel build

[philippe-granet]

What's changed?

Since PR #720 merged, I made more tests on different projects, and there is some cases where recipes are still executed before the end of all module packaging when building with Maven parallel build .

I analyzed the implementation of the installAtEnd and deployAtEnd options of the maven-install-plugin:
https://github.com/apache/maven-install-plugin/blob/master/src/main/java/org/apache/maven/plugins/install/InstallMojo.java
and maven-install-plugin plugins:
https://github.com/apache/maven-deploy-plugin/blob/master/src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java

It uses mojo Context to store "state markers", presence of marker means project was "processed".

This MR is based on this implementation.

What's your motivation?

Fix #719

Anyone you would like to review specifically?

@timtebeek

Any additional context

I have added a RewriteRunParallelIT test, with a Maven project that have 2 modules a and b.
These 2 modules are build in parallel (@MavenOption(value = MavenCLIOptions.THREADS, parameter = "2").
And I've added a sleep Antrun task in module a, in order to force module a finish building after module b.`

Without this MR, this test fail, because previous implementation:
List<MavenProject> sortedProjects = mavenSession.getProjectDependencyGraph().getSortedProjects();
always return [a,b] project list in this order, even if module a is longer to build than module b.

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[timtebeek]

Thanks a lot for coming back with the detailed fix!