Refactor pytest Actions workflow and group integration tests

[BrianJKoopman]

Description

This PR contains several improvements to the way we are running our test workflow:

• Split unit test, integration tests, and coverage upload to separate jobs (similar to what we did in ocs in Refactor pytest GitHub Actions workflow ocs#448)
• Groups the integration tests and runs them in separate jobs
• Replaces the cancel-workflow-action with built in concurrency configuration

While adding testing across Python versions in the unit tests I found issues with installation in both Python 3.7 and 3.12. The 3.12 problem will be solved with #1035. The 3.7 problem is not worth fixing, so we drop 3.7 support.

Motivation and Context

I've been meaning to do the same refactor I did in ocs in simonsobs/ocs#448.

I was simultaneously motivated to group and split the integration tests because those have been flaky lately and I'm not sure which test is causing the flakiness. Grouping will at least help narrow down the list and cancel/rerun individual groups, while also decreasing the overall time it takes for the workflow to run -- now under 10 minutes!

Lastly, the cancel-workflow-action hasn't been needed since they introduced native concurrency limits within Actions. See simonsobs/ocs#468.

How Has This Been Tested?

I tested this with a temporary on: push. It's working well after the kinks were worked out: https://github.com/simonsobs/socs/actions/runs/24098038868

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.