[MNG-7720] Wrong build order of forked projects (#1039)

The original fix MNG-7672 matched the "scope" but missed the "order". `project.collectedProjects` are in order as loaded (POM order), is not topologically sorted.

Fix is to use DAG of projects, ask for downstream projects (will return more then we need but sorted) and narrow that list to only contain collected projects.

---

https://issues.apache.org/jira/browse/MNG-7720

maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleDependencyResolver.java

@@ -26,6 +26,7 @@
 import java.util.Collections;
 import java.util.HashMap;
 import java.util.HashSet;
+import java.util.Iterator;
 import java.util.LinkedHashSet;
 import java.util.List;
 import java.util.Map;
@@ -97,9 +98,18 @@ public static List<MavenProject> getProjects( MavenProject project, MavenSession
     {
         if ( aggregator && project.getCollectedProjects() != null )
         {
-            List<MavenProject> projects = new ArrayList<>();
-            addProjectAndSubModules( projects, project );
-            return projects;
+            List<MavenProject> sortedProjects = new ArrayList<>( session.getProjects() ); // sorted but all
+            List<MavenProject> projectAndSubmodules = new ArrayList<>();
+            addProjectAndSubModules( projectAndSubmodules, project ); // not sorted but what we need
+            Iterator<MavenProject> sortedProjectsIterator = sortedProjects.listIterator();
+            while ( sortedProjectsIterator.hasNext() )
+            {
+                if ( !projectAndSubmodules.contains( sortedProjectsIterator.next() ) )
+                {
+                    sortedProjectsIterator.remove();
+                }
+            }
+            return sortedProjects;
         }
         else
         {