Rename the top-level requirements.txt file.

Some tools cannot help themselves: they see a `requirements.txt` file,
and immediately they assume it is intended for them and they MUST try to
install whatever it contains.

No, `mkdocs-deploy-gh-pages`, those requirements ARE NOT FOR YOU!

Author: gouttegd

Makefile

@@ -156,7 +156,7 @@ publish-multiarch-dev:
 		.
 
 # This should use the same base image as the one used to build the ODK itself.
-constraints.txt: requirements.txt
+constraints.txt: python-requirements.txt
 	docker run -v $$PWD:/work -w /work --rm -ti ubuntu:24.04 /work/scripts/update-constraints.sh --in-docker
 
 clean-tests:

docker/builder/Dockerfile

@@ -37,7 +37,7 @@ RUN apt-get update && \
 # Therefore we install all of them on the builder image (where we have
 # all the build tools required to compile them if needed), and we'll
 # copy the entire Python tree to the final images.
-COPY requirements.txt /build/requirements.txt
+COPY python-requirements.txt /build/requirements.txt
 COPY constraints.txt /build/constraints.txt
 COPY pip-constraints.txt /build/pip-constraints.txt
 RUN find /usr/lib/python3/dist-packages -type d -name '*-info' | \

requirements.txt python-requirements.txtrequirements.txt renamed to python-requirements.txt

@@ -31,7 +31,7 @@ fi
 virtualenv -p ${PYTHON_VERSION:-3.12} tmpdir
 . tmpdir/bin/activate
 [ -f pip-constraints.txt ] && export PIP_CONSTRAINT=$(pwd)/pip-constraints.txt
-python3 -m pip install -r requirements.txt
+python3 -m pip install -r python-requirements.txt
 python3 -m pip freeze | grep -v ^odk-core > constraints.txt
 
 test -n "$(head constraints.txt)"