Java Maven Projects containing other nested Java Maven Projects not being recognized as Java Projects in 1.17

Description

I admit that our project structure is not standard, but it's how we've been working for many years. We have a java (war) project that contains many Java (jar) projects in a folder structure similar to the one below.

**root_java_project**
|-> pom.xml
|-> src
|-> **child_java_project_1**
      |-> pom.xml
      |-> src
|-> **child_java_project_2**
      |-> pom.xml
      |-> src
...
|-> child_java_project_n
      |-> pom.xml
      |-> src

Several on our team recently experienced this issue when we updated to Java Extension Pack to 1.17. It immediately ceased recognizing our ROOT project as being a legit java project. The child projects were fine. (note that the project hierarchy is only one level deep -- a root and it's children). Reverting back to 1.16 or earlier made the issue disappear.

Environment

• Operating System: Mac OS Ventura 13.13.1
• JDK version: 17 and 16
• Visual Studio Code version: 1.77.3
• Java extension version: 1.17

Steps To Reproduce

1. Assume folder structure as shown above.
2. Open an empty workspace
3. click Add folder to workspace and select child_java_project_1
4. project is added to workspace and it's recognized as a java project
5. repeat for child_java_project_2 ... child_java_project_n
6. all projects are recognized as java projects with full linking, debugging, etc, support.
7. finally repeat for root_java_project. It shows up in the "Java Projects" but it doesn't recognize that there's a pom in that root folder and consequently doesn't capture it as being a legit java project.
8. Revert back to 1.15 or 1.16 and it works.

I do see quite of few Stack Overflows in the Language Server Log file. Not sure if that's the cause.

VS Code Language Server Log file.txt
VSCode Client Logs.txt

Current Result

Expected Result

Additional Informations

Comienza reproduciendo la estructura anidada del workspace con pom.xml descrita en la issue y, a continuación, inspecciona el VS Code Language Server Log y los VSCode Client Logs adjuntos en busca de los Stack Overflows reportados. Se considera terminado cuando el proyecto Java raíz se reconoce con su pom.xml y la compatibilidad existente con proyectos hijo sigue funcionando en Java extension 1.17.