[2] Add tox gen check to CI

[sentrivana]

Similar to split_tox_gh_actions, run the tox generation script in CI and compare the resulting tox.ini to the committed one. If there are changes, this most likely means someone edited tox.ini directly instead of the template. Make the check fail in that case.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.20%. Comparing base (c2c6450) to head (b7219bc).
Report is 3 commits behind head on ivana/tox-script-1.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@                  Coverage Diff                   @@
##           ivana/tox-script-1    #3972      +/-   ##
======================================================
- Coverage               80.20%   80.20%   -0.01%     
======================================================
  Files                     139      139              
  Lines                   15394    15394              
  Branches                 2596     2596              
======================================================
- Hits                    12347    12346       -1     
+ Misses                   2202     2201       -1     
- Partials                  845      847       +2     

see 2 files with indirect coverage changes

[sentrivana]

I will close this one. It'd actually bug us not just when there were manual edits, but also if a new version of a tested framework came out. Have to figure out a better way for this.