Should support polyglot projects better

Java projects are not automatically detected when a polyglot project is opened in VS Code. For example, microservice app (e.g. https://github.com/elgris/microservice-app-example) usually places each service into a separate folder, see the structure below. Since the root folder doesn't have any build file, Java extensions are not be activated automatically. Every time users have to open a Java file before using any Java feature, which is not convenient.

microservice
├── frontend
│   ...
│   └── package.json
├── backend
│   ...
│   └── pom.xml
└── README

To support polyglot project better, we can relax the activation event a little bit. For example, allow detection of build files from direct subfolders. VS Code activation events support glob pattern, which we can implement using workspaceContains:*/pom.xml. The glob pattern */pom.xml only scans two levels of directories and doesn't add much scanning cost.

    "workspaceContains:*/pom.xml",
    "workspaceContains:*/build.gradle",
    "workspaceContains:*/settings.gradle",
    "workspaceContains:*/build.gradle.kts",
    "workspaceContains:*/settings.gradle.kts",

This feature request applies to all Java extensions under Java pack.

Comienza localizando los activationEvents de las extensiones de Java y compara sus patrones actuales de workspaceContains con los patrones direct-subfolder propuestos. Verifica el cambio con un workspace políglota cuyos archivos de compilación de Java estén un nivel por debajo de la raíz, y confirma que las funcionalidades de Java se activan sin abrir primero un archivo Java.