Replace the link to the coverage community guide with a link to the .NET Code Coverage documentation

[andrei-epure-sonarsource]

The new docs containing instructions for setup of coverage in .NET are the first time we have had really clear instructions. Previously we relied on a Community Post that is great but far from simple. The new documentation is not easy to find after a basic setup user journey so we should point to it where possible.

If there is a problem with finding or importing the coverage file a message in the logs currently points to the Community Post. We should add a link to the documentation in either the SQ or SC first.

See in CoverageAggregator

• https://github.com/SonarSource/sonar-dotnet/blob/8.43.0.51858/sonar-dotnet-shared-library/src/main/java/org/sonar/plugins/dotnet/tests/CoverageAggregator.java#L131
• https://github.com/SonarSource/sonar-dotnet/blob/8.43.0.51858/sonar-dotnet-shared-library/src/main/java/org/sonar/plugins/dotnet/tests/CoverageAggregator.java#L144

Actual:

• https://community.sonarsource.com/t/37151

Expected:

• https://docs.sonarqube.org/latest/analysis/test-coverage/dotnet-test-coverage/
• https://docs.sonarcloud.io/enriching/test-coverage/dotnet-test-coverage/

[andrei-epure-sonarsource]

I'm removing this from the Kanban because I need to say here how to tell whether we're on SQ or SC. Because the URLs are different.

And TBH we should probably ask Marketing to create Redirect links for each. In case the URL breaks, we should change the Redirect, not the code.