Rebuild All, Rebuild Project and Reload all Maven Projects trigger maven phases up to process-test-classes

Since version 1.14.0 the actions Rebuild All, Rebuild Project and Reload all Maven Projects trigger maven phases up to process-test-classes. For us this leads to a huge performance issue (vscode even hangs up) since we use a multi project workspace with multiple maven project that each need to do some expensive stuff (javascript dojo build) in phase process-sources.
Up until now this worked in eclipse and vscode with java extension 1.13.0 like a charm, since both never executed this phase in the UI if not explicitly triggered by a maven build.
Is it by intention or is this a bug? If it is, is there any possibilty to turn this off or any other solution available?

Environment

• Operating System: Win 10
• JDK version: jdk-17.0.3.1
• Visual Studio Code version: 1.74.3
• Java extension version: 1.14.0

Steps To Reproduce

1. Import the project
2. change the file path in the ant plugin in the pom.xml to a path in your system
3. Click Rebuild All
4. Now you see, that the file is created and lines are appended whenever one of the actions is executed.

Same steps in version 1.13.0 never writes the file as the phase is not executed.

demo.zip

Current Result

Phase process-sources is executed.

Expected Result

Phase process-sources is not executed like in v1.13.0.

Additional Informations

none

Reproduce el comportamiento con el demo.zip proporcionado, cambiando la ruta en el ant plugin de pom.xml, y compara Rebuild All entre las versiones de la extensión 1.13.0 y 1.14.0. Traza qué fases del ciclo de vida de Maven invocan esas acciones; se considera completado cuando process-sources ya no se ejecuta mediante estas acciones de la UI, coincidiendo con el resultado esperado.