Enabling java.autobuild.enabled causes the spring.profiles.active to be set to the default profile irrespective of the profile used for the maven build

Issue Type: Bug

1. Create a Spring.Boot application
2. Create two profiles in the pom.xml -

<profiles>
  <profile>
    <id>uat</id>
    <properties>
      <maven.test.skip>true</maven.test.skip>
      <activatedProperties>uat</activatedProperties>
    </properties>
    <build>
      <finalName>${project.artifactId}-${project.version}-uat</finalName>
    </build>
  </profile>

  <profile>
    <id>dev</id>
    <activation>
      <activeByDefault>true</activeByDefault>
    </activation>
    <properties>
      <activatedProperties>dev</activatedProperties>
      <maven.test.skip>true</maven.test.skip>
    </properties>
    <build>
      <finalName>${project.artifactId}-${project.version}-dev</finalName>
    </build>
  </profile>
</profiles>

3. Create an application.properties file for the Spring.Boot application and add the following -
   spring.profiles.active=@activatedProperties@
4. Set "java.autobuild.enabled": true in settings.json
5. Execute a maven build from within the VS Code environment -
   mvn clean package -Puat
6. Note the contents of the target application.properties file which will contain -
   spring.profiles.active=dev
7. Set "java.autobuild.enabled": false in settings.json
8. Execute a maven build from within the VS Code environment -
   mvn clean package -Puat
9. Note the contents of the target application.properties file which will contain -
   spring.profiles.active=uat

Note: If VS Code is closed and the maven command is used from a command window then the issue does not occur.

Extension version: 0.10.0
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z)
OS version: Windows_NT x64 10.0.14393

Riprodurre il problema con settings.json abilitando java.autobuild.enabled, utilizzando i profili Maven e confrontando il file application.properties generato dopo mvn clean package -Puat. Tracciare il punto di ingresso della compilazione automatica Java di VS Code e verificare che il profilo generato rimanga uat, come in una compilazione eseguita al di fuori di VS Code.