fix coverage reporting

[rkm]

Proposed Changes

coverlet.msbuild was becoming buggy and hard to deal with, so we switch to the dotnet-coverage (Microsoft.CodeCoverage) tool which now seems stable and can generate the same report format.

This also uploads the coverage report as a build artifact to make it easier to debug CI runs.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that would cause existing functionality to not work as expected)
• Documentation-Only Update (if none of the other choices apply)
  • In this case, ensure that the message of the head commit from the source branch is prefixed with [skip ci]

Checklist

By opening this PR, I confirm that I have:

• Reviewed the contributing guidelines for this repository
• Ensured that the PR branch is in sync with the target branch (i.e. it is automatically merge-able)
• Updated any relevant API documentation
• Created or updated any tests if relevant
• Created a news file
  • NOTE: This must include any changes to any of the following files: default.yaml, any of the RabbitMQ server configurations, GlobalOptions.cs
• Listed myself in the CONTRIBUTORS file 🚀
• Requested a review by the @SMI/Reviewers team

Issues

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.79%. Comparing base (8dfa2c0) to head (3f7e43c).

Additional details and impacted files

@@            Coverage Diff             @@
##            main    #1901       +/-   ##
==========================================
+ Coverage   0.00%   80.79%   +80.79%     
==========================================
  Files        177      309      +132     
  Lines       6548    15397     +8849     
  Branches     898     1366      +468     
==========================================
+ Hits           0    12440    +12440     
+ Misses      6548     2541     -4007     
- Partials       0      416      +416     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.