Refactor integration tests: Remove version ranges and implement automatic test ordering

[gnodet]

Overview

This comprehensive refactoring modernizes the Maven integration test suite by removing version range dependencies from constructors and implementing automatic test ordering for better concurrent execution.

Key Changes

🔧 Core Refactoring

• Removed version range constructors from AbstractMavenIntegrationTestCase
• Updated 500+ integration test classes to remove version range parameters from constructors
• Replaced version constraints with standard @since javadoc tags and @Disabled annotations
• Removed empty constructors that only contained super(); calls

📋 Test Ordering

• Implemented TestSuiteOrdering class for consistent test execution
• Orders tests by prefix (gh-xxx, mng-xxx, it-xxx) in descending order
• Ensures newer tests run first for better fail-fast behavior in concurrent execution
• Replaces the previous TestSuiteOrdering with improved automatic ordering logic

🎯 Examples of Changes

Before:

public class MavenIT0051ReleaseProfileTest extends AbstractMavenIntegrationTestCase {
    public MavenIT0051ReleaseProfileTest() {
        super("(2.0.2,4.0.0-alpha-1)");
    }
}

After:

@Disabled("Bounds: (2.0.2,4.0.0-alpha-1)")
public class MavenIT0051ReleaseProfileTest extends AbstractMavenIntegrationTestCase {
    // Constructor removed - no longer needed
}

Benefits

✅ Cleaner Codebase: Removed over 2,500 lines of boilerplate code
✅ Better Documentation: Version constraints now clearly documented via standard annotations
✅ Improved Test Execution: Automatic ordering ensures newer tests run first for faster feedback
✅ Maintainability: Easier to understand and modify test constraints
✅ Backward Compatibility: All existing functionality preserved while removing technical debt

This refactoring makes the integration test suite cleaner and more maintainable.

---

Pull Request opened by Augment Code with guidance from the PR author