Use coverage flags to distinguish between runs

[urfeex]

Currently, we run separate coverage jobs for the different software versions. We run unit and integration tests for

• The lowest supported CB3 version with a UR5 (Currently 3.14.3)
• The lowest suppoted PolyScope 5 version with a UR5e (Currently 5.9.4)
• The latest PolyScope 5 version with a UR20

All of these gather coverage data, but take different branches in the code due to version-dependent execution. As we generate and upload coverage data for all of them, coverage data varies slightly. This approach uses individual flags for each matrix entry. I am not 100% sure whether this does what we want, but I want to give it a try.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.45%. Comparing base (2c12bee) to head (4b56569).
Report is 28 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #261      +/-   ##
==========================================
+ Coverage   71.71%   73.45%   +1.74%     
==========================================
  Files          71       76       +5     
  Lines        2786     2969     +183     
  Branches      353      379      +26     
==========================================
+ Hits         1998     2181     +183     
+ Misses        596      588       -8     
- Partials      192      200       +8     

Flag	Coverage Δ
ur20-latest	72.00% <ø> (?)
ur5-3.14.3	72.60% <ø> (?)
ur5e-5.9.4	72.33% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[urrsk]

Seems to work