Add a nox session for regenerating pinned requirements files used in CI

[namurphy]

This PR adds a nox environment that can be used to regenerate requirements files. It can be run with nox -s requirements. The intention of this nox environment is to eventually replace the current tox environment, but the removal of the tox environment will come after sessions for running tests get added to noxfile.py...hopefully soon.

This PR also standardizes the naming scheme for the requirements files, ideally making the names of the files better reflect what they are used for.

All of the files in ci_requirements/ are auto-generated, so they probably be mostly skipped during the review.

Only a couple pull requests into this, and I'm already hoping I never have to edit a tox.ini file ever again! 😹

Related issues

#1734, #1735, #2647, #2654, #2656

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.88%. Comparing base (79b1c19) to head (f454ee0).

❗ Current head f454ee0 differs from pull request most recent head b3d6ce4. Consider uploading reports for the commit b3d6ce4 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2664      +/-   ##
==========================================
- Coverage   95.21%   94.88%   -0.33%     
==========================================
  Files         103      103              
  Lines        9412     9412              
  Branches     2155     2155              
==========================================
- Hits         8962     8931      -31     
- Misses        273      299      +26     
- Partials      177      182       +5     

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

[namurphy]

I ran into a problem when I was running nox -e requirements locally with Python 3.12, without Python 3.10 installed, and when trying to resolve requirements for Python 3.10. I ended up getting:

nox > python -m uv pip compile pyproject.toml --upgrade -p 3.10 --extra tests -o ci_requirements/tests-3.10-highest.txt
error: Querying Python at `/usr/bin/python3` failed with status exit status: 1 with exit status: 1
--- stdout:

--- stderr:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/run/media/namurphy/d423d80e-c227-4a33-b50f-545b44160ce3/namurphy/.cache/uv/.tmppRkEoP/python/get_interpreter_info.py", line 536, in main
    "platform": get_operating_system_and_architecture(),
  File "/run/media/namurphy/d423d80e-c227-4a33-b50f-545b44160ce3/namurphy/.cache/uv/.tmppRkEoP/python/get_interpreter_info.py", line 439, in get_operating_system_and_architecture
    from .packaging._manylinux import _get_glibc_version
  File "/run/media/namurphy/d423d80e-c227-4a33-b50f-545b44160ce3/namurphy/.cache/uv/.tmppRkEoP/python/packaging/_manylinux.py", line 1
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
---
nox > Command python -m uv pip compile pyproject.toml --upgrade -p 3.10 --extra tests -o ci_requirements/tests-3.10-highest.txt failed with exit code 2
nox > Session requirements failed.

Will have to look into this later...

[namurphy]

📝 Some differences between nox and tox

• A tox environment corresponds to a nox session.
• Similarly, the flag used to invoke a nox session should preferably be nox -s requirements (instead of -e, though -e also works, presumably for cross-compatibility with tox).

[namurphy]

One of the benefits of switching to nox is that we can define functions to help create testing environments!

[namurphy]

I ran into a problem when I was running nox -e requirements locally with Python 3.12, without Python 3.10 installed, and when trying to resolve requirements for Python 3.10.

It turns out that this problem occurred on my workstation at work (running RHEL) but did not occur on my home computer (running Ubuntu 22.04).

This PR is going to wait until after the 2024.5.0 release.

[namurphy]

Because the requirements filenames are changing, we'll need the files generated by tox for the remaining tox environments, as well as the files generated by nox for the current and forthcoming nox sessions. It'll be messier having duplicate requirements files under different names, but I want to switch things over completely soon.

[ejohnson-96]

👍