add apply plugin: "net.serenity-bdd.serenity-gradle-plugin" to build.gradle, then vscode is not able to recognize the project as a java project

adding apply plugin: "net.serenity-bdd.serenity-gradle-plugin" to build.gradle, then vscode is not able to recognize the project as a java project

Environment:

• VS Code Version: 1.85.1
• Extension Version: Extension Pack for Java v0.25.15
• JDK Type & Version: Oracle, v11.0.8
• OS Type & Version: windows

Step to Reproduce:

1. Have a standard alone java starter gradle project, e.g. we use spring gradle sample java project from https://github.com/spring-guides/gs-gradle, download the project to local machine, and upgrade gradle to version 8.2.1
2. using vscode open folder complete of the project
3. at this point, we can run gradle build of the project, vscode recognize this project as a java project, and shows all objects and libs info in tab "JAVA PROJECTS"
4. now open build.gradle file and add the following plugin:
   plugins {
   id "net.serenity-bdd.serenity-gradle-plugin" version "4.0.30"
   }
5. run ./gradlew clean build
6. right click tab "JAVA PROJECTS" and select "clean workspace"
7. wait for vscode clean workspace is done, you will see below message under tab "JAVA PROJECTS"
   No java projects found in the current workspace. you can open a java project folder......

Expected Behavior:
at step 7. we should see the updated java objects and libs information under tab "JAVA PROJECTS"

Actual Behavior:
vscode does not recognize the java project any more and you will see below message under tab "JAVA PROJECTS"
No java projects found in the current workspace. you can open a java project folder......

Related Issues:
No

build.gradle.txt

Reproduziere das Problem mit dem spring-guides gs-gradle-Projekt, Gradle 8.2.1, VS Code und dem Serenity Gradle plugin in build.gradle. Vergleiche zunächst Java Projects vor und nach dem Ausführen von clean build und Clean Workspace; abgeschlossen ist es, wenn das Projekt sowie seine Java-Objekte und Bibliotheken nach dem Hinzufügen des Plugins weiterhin erkannt werden.