[MNG-6772] Re-enable integration test for nested import scope repository override (#11826) (#12231)

The test was disabled in 2021 after the fix was reverted twice.
Maven 4's session-based architecture fixes the root cause: the new
DefaultModelBuilder properly propagates user-configured repositories
(including central overrides) through nested import scope resolution.

Both test scenarios (testitInProject and testitInDependency) now pass.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: gnodet

its/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng6772NestedImportScopeRepositoryOverride.java

@@ -20,7 +20,6 @@
 
 import java.io.File;
 
-import org.junit.jupiter.api.Disabled;
 import org.junit.jupiter.api.Test;
 
 /**
@@ -33,7 +32,6 @@
  * The test confirms that the dominant repository definition (child) wins while resolving the import POMs.
  *
  */
-@Disabled // This IT has been disabled until it is decided how the solution shall look like
 public class MavenITmng6772NestedImportScopeRepositoryOverride extends AbstractMavenIntegrationTestCase {
 
     public MavenITmng6772NestedImportScopeRepositoryOverride() {