Extract method refactoring leads to inconsistent code behavior.

[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 "return;"
2. click “Refacator-Extract to method”

public class OriginalClass {
public void foo() {
Object runnable= null;
Object[] disposeList= null;
for (int i=0; i < disposeList.length; i++) {
if (disposeList [i] == null) {
disposeList [i] = runnable;
// extract method
return;
}
}
}
}

refactoring result:

Reason: The extraction method does not contain a return statement. If inline refactoring is performed on the extraction method, the behavior of the statement before and after refactoring is inconsistent.

Expected behavior: Check for statements like return, provide a prompt before refactoring, and do not allow extraction method refactoring.

Reproduce the case in the Java extension using the supplied OriginalClass example and the listed VS Code and JDK versions. Trace the Extract to method refactoring entry point; done means the refactoring detects the return statement, prompts as appropriate, and does not permit an unsafe extraction.