Do not use pip-install; add dependency cooldowns

[JelleZijlstra]

Zizmor recommends against pip-install (https://docs.zizmor.sh/audits/#misfeature).

Also add dependency cooldowns to prevent supply-chain compromises.

[github-actions]

diff-shades results comparing this PR (e9406ab) to main (8049246):

--preview style: no changes

--stable style: no changes

---

What is this? | Workflow run | diff-shades documentation

[cobaltt7]

Zizmor recommends against pip-install because it installs dependencies to the global scope and makes them vulnerable to dependency conflicts. This change does the same thing, just without being flagged by Zizmor. The correct fix to this would be to create a venv inside the workflow and install dependencies there. IMO that's overkill and unnecessary because there's only one pip-install per job and not much opportunity for conflicts

[cobaltt7]

setup-python 7.0.0 has removed the input: actions/setup-python#1336
Note again that this change is effectively the same as using pip-install, and installs into the runner-level environment. Again, I don't think this is an issue because we don't run multiple install commands or mix multiple tools. The proper fix to this would be to use a venv in each workflow, which to me feels like overkill, and IMO GHA should always have a quick-and-dirty way to install packages. It makes most sense to me to keep this until/unless it stops working

Would it be a bad idea to set PIP_UPLOADED_PRIOR_TO=P2D as a repository env value instead? That avoids repetition in workflow files and the possibility of forgetting to include it.