Renaming module folders is not synchronized with the Java Project Manager and may result in renaming ghost folders

Description: The Java Project Management view fails to synchronize with file system changes. When renaming a module folder via the file explorer, the Java Language Server does not detect or reflect the rename operation, resulting in a desynchronization between the project metadata and the actual file system state. The recreation of the old folder is a side effect of this synchronization failure.

Build Tool: Maven
OS: Windows 11 25H2

Steps to Reproduce:

1. Open a workspace folder that contains multiple Java sub-projects (modules).
2. Wait for the Java Language Server to finish importing and indexing all projects.
3. 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.
4. Observe the Java Project Explorer/Manager view.

Actual Result:

• The Java Project Manager still displays old-module-name.
• The system recreates a new folder named old-module-name in the file system containing target and other
  directories (side effect of the sync failure).
• 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 operation.
• The project metadata should be updated or re-indexed to reflect the name change, maintaining synchronization with
  the file system.

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 confirms that the Language Server's cache retains stale file paths and
fails to monitor file system rename events, causing the desynchronization and subsequent side effects.

Reproduce el cambio de nombre después de importar un proyecto Java y, a continuación, comienza con el comportamiento del comando Java: Clean Workspace Cache y de la sincronización del servidor de lenguaje descrito en el informe. Se considera terminado cuando Java Project Manager refleja el nuevo nombre de la carpeta sin volver a crear la carpeta antigua, y la carpeta renombrada sigue vinculada como módulo Java.