make rialto-airflow dependency management consistent across local dev, CI, and dockerized airflow

[jmartin-sul]

Per post-standup discussion: our Dockerfile has airflow installing dependencies from requirements.txt, see

rialto-airflow/Dockerfile

Line 14 in ec6bbd2

RUN uv pip install --no-cache "apache-airflow==${AIRFLOW_VERSION}" -r requirements.txt

But in local dev and in CI, we use the uv.lock, because we uv run ... everything (e.g. uv run pytest).

We should use a single consistent approach for running things and for specifying dependencies. That might be compiling to and installing from requirements.txt, since that might be what we have to use in the Airflow Dockerfile?

[edsu]

I think that #160 will help with this!