The GetAnalyzerSettings task is removing existing source generators for test projects when sonar.dotnet.excludeTestProjects is set to true

[csaba-sagi-sonarsource]

The issue was originally reported by the community: https://community.sonarsource.com/t/sonarqube-scanner-seems-to-interfere-with-net-source-generators-refit/82712

Reproduction steps

1. Create a test project that uses classes that are generated by a source generator
2. Make sure sonar.dotnet.excludeTestProjects is set to true
3. call begin step
4. call dotnet build -> this will fail because the source generator was removed by the GetAnalyzerSettings, so the generated type is not generated and is unknown in the test project.

Version used:

dotnet-sonarscanner 5.11.0

[csaba-sagi-sonarsource]

Should have a very similar solution like #1211

[PavelFischerCoupa]

We run into the similar issue: If we use sonar, generator output is not present in the compiled dll. Any plans to fix it, or is there any workarounds? But in our case it is independent of setting. We use version 5.15 for dotnet-sonarscanner and server Version 8.3.1