ci: use tox in ci

[moe-ad]

Related to #296

[moe-ad]

Moving to "Ready for review" so I can observe workflow runs.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.52%. Comparing base (678564f) to head (78a278b).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2031      +/-   ##
==========================================
- Coverage   88.55%   86.52%   -2.04%     
==========================================
  Files          90       90              
  Lines       10225    10225              
==========================================
- Hits         9055     8847     -208     
- Misses       1170     1378     +208     

[moe-ad]

Tests run fine now but overall takes twice as long as current CI workflow.
Maybe we can test tox-uv out here @jorgepiloto? I can see much of the delay is due to the time it takes tox to spin up a new environment for each test target.

But at least we are now benefitting from the fact that each testing environment is clearly isolated, and random PyDPF test failures should occur sparingly in this case.

[jorgepiloto]

This is great news, @moe-ad. Let's give it a try to ' tox-uv' plugin, in that case. Just to make sure the bottle neck is now Tox installing all the necessary dependencies for every environment.

[moe-ad]

pytest-xdist seems problematic in retro versions. May have to remove it for those.
More than 15 mins being saved by using uv from my observation, but still not low enough.
One other thing to try is activating caching.
Tests need to run in 30 mins or less for this to be a solid replacement for current CI workflow.