Fix SonarCloud coverage always reporting 0%

[Copilot]

• Investigate root cause: Microsoft.Testing.Extensions.CodeCoverage generates empty cobertura XML files (<packages /> with no data), causing 0% coverage in SonarCloud
• Fix sonarcloud.yml workflow:
  • Replaced dotnet-reportgenerator-globaltool with dotnet-coverage tool installation
  • Use dotnet-coverage collect to properly capture coverage data as VS Coverage XML
  • Use sonar.cs.vscoveragexml.reportsPaths instead of sonar.coverageReportPaths
  • Removed the reportgenerator conversion step (no longer needed)
  • Changed build flag from --no-restore to --no-incremental as required by the SonarSource docs — this ensures all files are rebuilt so SonarScanner can instrument them

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[304NotModified]

@copilot still won't work. Read the docs

[Copilot]

@copilot still won't work. Read the docs

Fixed in 33267d7. The docs specify dotnet build --no-incremental — this is required so SonarScanner instruments all source files during the build. Using --no-restore was skipping that instrumentation step.