Cleanup the SonarQube.Integration.target file in a different way

[csaba-sagi-sonarsource]

trafficstars

The problem with the current approach is that if the build fails, users don't run the end step (not to push partial results) so the target file is not removed. This can cause our analyzers to be involved in other builds that the users were not planning to analyze. Issues reported by the community:

• https://community.sonarsource.com/t/sonarcloud-analysis-registration-not-always-cleaned-up-properly/82351
• https://community.sonarsource.com/t/sonarqube-impacting-seperate-agent-job/12328

[andrei-epure-sonarsource]

From Scanner Monthly;

• The stub is always left in the common folder (for when build agents share the same CI machine).

• The "link" is in the working directory (the other target files; the stub finds this link via environment variables). When the build fails, the working directory is not cleaned.

• scope: self-hosted Azure agents with multi-step pipelines.

[andrei-epure-sonarsource]

ToDo: narrow down the problem