Improve Codecov settings

[Vampire]

• Fail the CI build if the Codecov uploading failed.
• Show more detailed information in the Codecov comment.
• Do not update the Codecov comment 13 times, but post it after all 14 reports were uploaded.
• Ignore dates in coverage reports to not get "upload expired" because the report was taken from remote build cache.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.73%. Comparing base (2c7db77) to head (cf3ed4d).
Report is 87 commits behind head on master.

❗ Current head cf3ed4d differs from pull request most recent head 7224fea. Consider uploading reports for the commit 7224fea to get more accurate results

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1629      +/-   ##
============================================
+ Coverage     80.44%   81.73%   +1.28%     
- Complexity     4337     4550     +213     
============================================
  Files           441      445       +4     
  Lines         13534    14242     +708     
  Branches       1707     1802      +95     
============================================
+ Hits          10888    11640     +752     
+ Misses         2008     1938      -70     
- Partials        638      664      +26     

see 15 files with indirect coverage changes

[leonard84]

This seems like it is likely to break if we change the number of builds in the matrices, at least create a comment pointing to this file/line in the workflows.

Is there a way to somehow set this in the workflow and compute the number of builds from the matix?

[Vampire]

Indeed, if you upload more reports, you will then have comment updates again.
If you upload less reports, you will notice that no comment is coming in.

I personally always was a bit confused when the first comment reduces the coverage and then edits and edits come in that increase the coverage, so I thought I put this in alongside.
Actually I've read it in a newsletter and it was my main intent to set that property. :-D

I don't think you can calculate it from the matrix unless you add a parser that parses the workflow file and interprets it to calculate how many iterations it will be.

[Vampire]

We could change the workflow files to instead be written in Kotlin using https://github.com/typesafegithub/github-workflows-kt. That's a really nice project I use for all my GitHub workflows now. And that could indeed then be used to calculate the value and generate a step that updates the Codecov file.

[Vampire]

I added one commit that now calculates the value from the build matrix.
But I also marked the PR as "Draft" as it now depends on #1630.