Copilot/fix type hierarchy sorting

[carstenartur]

Implements a fix for issue #1865 to detect when moving a method would change which overloaded method gets called due to method resolution changes.

Problem

When moving a method to a class that has a superclass with a method of the same name but different parameter types, the refactoring could silently change which method gets called, leading to incorrect behavior.

Example from issue #1865:

• Class A has m(Object)
• Class B extends A
• Class C has m(String) to be moved to B
• In B.f(), the call m("1") currently resolves to A.m(Object)
• After moving C.m(String) to B, the call would resolve to B.m(String) instead

This is a semantic change that should be detected and reported as an error.

Solution Implemented

Added a new check method checkOverloadResolutionChanges() in MoveInstanceMethodProcessor that:

1. Examines the target type's hierarchy for methods with the same name as the method being moved
2. Detects when parameter types differ (indicating potential overload resolution changes)
3. Reports an error when such a conflict is found, preventing the refactoring
4. Includes progress monitoring for large type hierarchies
5. Provides proper error handling with warning messages if hierarchy analysis fails

Changes Made

1. MoveInstanceMethodProcessor.java:

   • Added checkOverloadResolutionChanges() method with progress monitoring
   • Integrated the check into checkFinalConditions() with proper progress tracking
   • Added error handling for hierarchy analysis failures

2. RefactoringCoreMessages.java & refactoring.properties:

   • Added error message: MoveInstanceMethodProcessor_overload_resolution_change
   • Added warning message: MoveInstanceMethodProcessor_hierarchy_not_available

3. Test Resources:

   • Created test case testFailOverloadResolution with the exact scenario from issue “Move method refactoring” causes the method call relationship to change #1865

The fix now correctly prevents the move method refactoring when it would change which overloaded method gets called, addressing the exact scenario described in issue #1865.

What it does

How to test

Author checklist

• I have thoroughly tested my changes
• The change is following the coding conventions
• I have signed the Eclipse Contributor Agreement (ECA)