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

…CI (#2664)

* Add nox to tests and docs requirements

* Add requirements environment to nox

* Have uv pip compile be quiet

* Run nox -s requirements

* Update noxfile.py

* Update & rename nox-generated requirements files

* Apply resolution strategy

* Update lowest direct requirements

* Edit changelog: 2664.internal.rst

* Remove the requirements files added by the nox session

* Clean up noxfile.py

* Add requirements files autogenerated by nox

* Add nox session to workflow updating pinned reqs

* Make it so that a session needs to be defined when running nox

Running `nox` will now make it print out a help message along with
the list of sessions.

* Remove comments used as section headers

.github/workflows/update-pinned-reqs.yml

@@ -24,11 +24,17 @@ jobs:
         python-version: 3.12
 
     - name: Install tox and its extensions
-      run: python -m pip install --upgrade tox tox-uv
+      run: python -m pip install --upgrade tox tox-uv nox uv
 
-    - name: Rebuild requirements
+    # Temporarily use requirements files generated both by tox and nox
+    # during the switchover from tox to nox.
+
+    - name: Rebuild requirements with tox
       run: tox -e requirements
 
+    - name: Rebuild requirements with nox
+      run: nox -s requirements
+
     # When a PR is created by a GitHub Action, normally the checks will
     # not be run. While the simplest workaround would have been to open
     # and close the PR, an alternative is to authenticate with GitHub

changelog/2664.internal.rst

@@ -0,0 +1,2 @@
+Converted the |tox| environment for regenerating the requirements files
+used in continuous integration checks to |nox|.