Fixing CI on stable branch

[YannickJadoul]

Several issues are currently breaking CI builds:

• NumPy 2 has a different repr of scalars (e.g., np.float64(496.3505526721194) instead of 496.3505526721194)
  • Fixed in b5c5ad0 and 93d6817
  • Is 93d6817 a good fix? Is this what we want?
  • Python 3.8 doesn't have a NumPy >= 2 version. Python 3.8 is also EOL since a month or two. So we could just scrap it, though I prefer to keep that for minor updates (i.e., 0.3.0), and not for patch updates (0.2.2). So we probably better just ignore those two doctests on Python 3.8.
• No abjad release supporting Python >= 3.12
  • I added 3.12 and 3.13 (04d0a88) cause we should probably be testing and supporting them, but so we cannot install abjad, currently.
  • Do we want to ping the abjad people? Do we want to find a way to get rid of the dependency? Do we just not want to test the abjad parts in CI on 3.12 and 3.13?
• No lilypond binary Python package for Apple Silicon (ARM)
  • The binaries (should) actually work, but I didn't get an answer yet to my issue: https://gitlab.com/jeanas/lilypond-wheels/-/issues/1
  • Same here, what to do? Drop this option? Add documentation? Just don't test? Or test back on a non-ARM image?
  • Cfr. No lilypond wheels for Apple Silicon #82

Misc changes:

• nPVI tests weren't updated after fix. But easily fixed: 7fb0d43 (and checked independently that this is the right value)
• Because of the shallow git checkout of the checkout action, tags and history weren't cloned. So setuptools_scm couldn't get the version number right, which confused me while tracking down other issues. Fixed in 7498a9f.

[YannickJadoul]

Python 3.8 doesn't have a NumPy >= 2 version. Python 3.8 is also EOL since a month or two. So we could just scrap it, though I prefer to keep that for minor updates (i.e., 0.3.0), and not for patch updates (0.2.2). So we probably better just ignore those two doctests on Python 3.8.

Fixed in b8f61a9, but:

• Is there a better solution?
• conftest.py in root or in thebeat/ (can't be in tests/, as it's not picked up for doctests there)
• Check for Python version or check for NumPy version?

[YannickJadoul]

No lilypond binary Python package for Apple Silicon (ARM)

Backported cefa9d9 from #82. Is this what we want, sweeping things under the rug for now?

[YannickJadoul]

Fixed in b8f61a9, but:

Drop current solution; just skip test for now, and reenable on main, while working toward 0.3.0

[YannickJadoul]

Same here, what to do? Drop this option? Add documentation? Just don't test? Or test back on a non-ARM image?

For now, keep as is, and don't test on mac ARM.
But check if there's a way of only installing the optional dependency on intel.

[YannickJadoul]

I added 3.12 and 3.13 (04d0a88) cause we should probably be testing and supporting them, but so we cannot install abjad, currently.

Pinged Abjad about this. Removing 3.12 and 3.13 CI configs for this PR, and adding them in a separate one!