Renaming a module folder does not sync with Java Project Manager and causes ghost folder recreation

[anzhiyubuchiyu]

Description: When opening a parent directory containing multiple Java projects (acting as modules), renaming a module folder via the file explorer does not trigger a synchronized update in the Java Project Management view. Instead, the system fails to recognize the new name and incorrectly recreates an empty directory with the original name.
Build Tool: Maven
OS: Windows 11 25H2

Steps to Reproduce:
Open a workspace folder that contains multiple Java sub-projects (modules).
Wait for the Java Language Server to finish importing and indexing all projects.
Rename one of the sub-project folders (e.g., rename old-module-name to new-module-name) using the OS file explorer or the IDE's built-in file tree.
Observe the Java Project Explorer/Manager view.

Actual Result:
The Java Project Manager still displays the old-module-name.
Automatically recreate a new folder named old-module-name in the file system that contains target and other directories.
The new-module-name folder is treated as an unlinked plain folder rather than a Java module.

Expected Behavior:
The Java Project Manager should detect the folder rename.
The project metadata should be updated or re-indexed to reflect the name change.

Additional Context:
Running the command "Java: Clean Workspace Cache" and restarting the language server resolves the issue and correctly reflects the new folder name. This suggests that the Language Server's cache is holding onto stale file paths and triggering the recreation of the old directory.