"No build tools" Java projects auto-import skipped due to presence of "build tools" Java projects in same workspace

Describe the bug
Java projects without build tools are being skipped during auto-import due to the presence of Java projects with build tools in the same workspace. This results in missing imports and project configuration issues.

To Reproduce
Steps to reproduce the behavior:

1. Create a workspace containing both Java projects with build tools (e.g., Maven, Gradle) and Java projects without build tools.
2. Clean the Java language server workspace to trigger auto-import on startup.
3. The Java projects without build tools fail to auto-import properly or are ignored/skipped by the extension, as they are not visible in the list of projects to import and do not import at all when opening any Java file in such projects.

Expected behavior
Java projects without build tools should be available as options to select in the import java projects list, allowing a non-build-tooled Java project to be imported correctly instead of skipped.

Environment

• Operating System: Windows
• JDK version: 21
• Visual Studio Code version: 1.111.0
• Java extension version: 1.53.0

Additional Information
When opening a Java file in a Java project without build tools, it will be automatically imported and added to the Java projects list, therefore auto-importing works fine as long as build tools projects aren't in the same workspace.

The best solution seems to be to add these types of projects to the list of importable Java projects and allow selection of non-build-tooled projects.

Reproduisez le problème dans Visual Studio Code avec un workspace contenant à la fois des projets Maven ou Gradle et des projets sans outils de build, puis nettoyez le workspace du Java language server afin de déclencher l’importation automatique au démarrage. Suivez la liste des projets importables et vérifiez que les projets sans outils de build y apparaissent et peuvent être sélectionnés et importés sans ouvrir d’abord un fichier Java.