Renaming methods causes code behavior to change

[provide a description of the issue]

Environment

Operating System: Windows11
JDK version: 17
Visual Studio Code version: 1.88
Java extension version: 1.29

Steps To Reproduce

1. select "k()"
2. click "Refactor-Rename"
3. new method name "m()"

In this example, before the rename, the f() method calls the m() method in the parent class, and after the rename, the f() method calls the method in the subclass renamed m(). The rename causes the code behavior to change, so it is a bug.

class A {
void m(Object m){
System.out.println("A");
}
}
class B extends A{
// rename k to m
void k(String m){
System.out.println("B");
}
void f(){
m("1");
}
}

Current Result:

Expected Result: A warning is given during the refactoring process that the name may cause the refactoring behavior to change

Additional Informations

Reproduziere das Problem im Refactor-Rename-Ablauf mit den bereitgestellten Java-Klassen, Windows 11, JDK 17, VS Code 1.88 und der Java extension 1.29. Verfolge, wie sich das Umbenennen von k in m auf den Aufruf in f() auswirkt, und überprüfe anschließend, dass das Refactoring warnt, wenn sich die Methodenauflösung ändern könnte.