Should not delete the project javanature when removing a nested .classpath resource file

[testforstephen]

Running JUnit Plugin Tests of org.eclipse.jdt.ls.tests in VS Code causes Java extension to delete javanature from .project file of org.eclipse.jdt.ls.tests project. This is because the test framework removes temporary test projects (e.g. eclipse.jdt.ls/org.eclipse.jdt.ls.tests/target/workingProjects/maven/salut/.classpath) after testing, which triggers a .classpath delete event as part of didChangeWatchedFiles event. The language server then deletes javanature of the parent project when it detects a .classpath delete event. This is annoying when you dogfood eclipse.jdt.ls development in VS Code.

Here are the reproducing steps:

1. Open the following eclipse-project in VS Code

eclipse-project
│   .classpath
│   .project
└───resources
        .classpath

2. Delete .classpath file under resources folder
3. You will see that javanature is removed from the .project file.