Use self-hosted macOS M2 runner to build macOS arm64 or universal wheels

[agriyakhetarpal]

@BradyPlanden and I, in conversation about the usage of the runner for the repository – have decided to look into building wheels for M-series platforms starting with PyBaMM v24.5rcX. This is since cross-compilation for SuiteSparse requires at least a version of 7.2.1, and we support 6.0.3, so we might not be able to do that yet on the standard GitHub Actions runners (see #3462).

In this scenario, this requires setting up a job in the PyPI workflows where the wheels can be built and passed as artifacts to the job that uploads them.

Whether to build a universal macOS wheel or an architecture-specific wheel can be discussed based on the wheel tags we are able to achieve, the macOS X version constraints for such wheels, and the size of the binaries generated.

[agriyakhetarpal]

From @Saransh-cpp on Slack: https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/

We can use GitHub Actions M1 runners for building the wheels since an ephemeral CI system will be preferred. We can continue to use the self-hosted M2 runner for testing purposes, though – it is certainly faster than regular runners.