Simplify test-python CI workflow

[odow]

Opening this PR for @galabovaa to take a look at.

The current .github/workflows files are very verbose. We can use build strategies instead of separate files for every possible job. Here's a simple one.

If there is interest, I'd propose that we do the others.

Also: do we need to run jobs on every push and pull_request? We end up with stuff like #2518 where we're running 309 jobs!!! (Most of which are duplicates)

WIth this change, CI would run:

• when you push to latest
• when you push to master
• when you open or update a pull request

CI would not run:

• when you push to a branch that does not have an open PR

This might be a downside, but it does nudge people to working in public PRs, rather than feature branches.

If we wanted to, we could add - "ci-*" which would trigger CI if a branch was named ci-foo.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.70%. Comparing base (26b632a) to head (9af5ef5).
⚠️ Report is 516 commits behind head on latest.

Additional details and impacted files

@@            Coverage Diff             @@
##           latest    #2551      +/-   ##
==========================================
- Coverage   79.71%   79.70%   -0.01%     
==========================================
  Files         346      346              
  Lines       86427    86427              
==========================================
- Hits        68894    68889       -5     
- Misses      17533    17538       +5     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[odow]

Is it necessary to test this mix of compilers? Why 11 on Mac but 12 and 13 on linux?

[odow]

Why 3.12 on Windows but 3.11 on Mac and linux?

[odow]

So @galabovaa, thoughts on simplifying some of the actions into a single file and using the build matrix?

[galabovaa]

As we discussed on our last Tuesday meeting, we will stick to development branches.

Build matrix yes, single file not for a while