Use macos-arm64 runners.

[joaander]

Description

Use the new GitHub Actions macos-arm64 runners.

Motivation and Context

Decrease the time needed to complete CI checks.

Checklist:

• I am familiar with the Contributing Guidelines.
• I agree with the terms of the Contributor Agreement.
• My name is on the list of contributors.
• The changes introduced by this pull request are covered by existing or newly introduced tests.
• The package documentation and framework documentation in signac-docs are up to date with these changes.
• I have updated the changelog and added any related issue and pull request numbers for future reference.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (da6fc8f) 69.27% compared to head (d8f0783) 69.27%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #806   +/-   ##
=======================================
  Coverage   69.27%   69.27%           
=======================================
  Files          48       48           
  Lines        4397     4397           
  Branches     1065     1065           
=======================================
  Hits         3046     3046           
  Misses       1142     1142           
  Partials      209      209           

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

[cbkerr]

Thanks!

[cbkerr]

Looks like they only support back to python 3.10 on arm64

Run actions/setup-python@v4
Installed versions
  Version 3.9 was not found in the local cache
  Error: The version '3.9' with architecture 'arm64' was not found for macOS 14.2.1.
  The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

[joaander]

47 minutes down to 42. Why does pytest take so long on Macs?

[joaander]

Looking at some slow tests:

• test_process_parallelized_project_status_homogeneous_schema spends 10 seconds inside <method 'acquire' of '_thread.lock' objects>.
• test_run_order, test_submit_status, and others spend all their time in built-in method posix.waitpid` (~10 seconds per call).

While these are running, there is very little CPU activity measured in htop. It seems that there might be a 10 second timeout somewhere that every one of these tests is triggering? In any case, this PR does not create the issue. I will investigate further at a later time.