setup to use a patched version of 3.14.4 for testing a garbage collection fix

[ewdurbin]

@zanieb prepared https://github.com/astral-sh/python-build-standalone/pull/1091/changes with a gc patch that seems to address the memory behavior we saw in our initial upgrade to 3.14:

memory usage for test.pypi.org from last 6 months, the elevated usage was 3.14

This sets up warehouse to run from a build with the patch from python-build-standalone #1091 as a diagnostic.

[ewdurbin]

FWIW I do not recommend we merge this as is, rather we would temporarily deploy test.pypi.org from the branch this PR introduces.

[zanieb]

As a note, we probably want to test astral-sh/python-build-standalone#1091 instead (which is just subbing 1091 instead of 1089) as that's the approach we're considering more seriously.

[ewdurbin]

As a note, we probably want to test astral-sh/python-build-standalone#1091 instead (which is just subbing 1091 instead of 1089) as that's the approach we're considering more seriously.

will bump.

[zanieb]

(I'll need to rebuild and publish that branch, so it'll be a minute)

[miketheman]

Closing for now, in favor of waiting for 3.14.5
https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014

[zanieb]

Hey! We still want to test this with a build of CPython 3.14 HEAD before the patch release.

The build is from astral-sh/python-build-standalone#1110

ARG PYTHON_STANDALONE_AMD64_URL=https://astral-sh-dev-artifacts.s3.us-east-2.amazonaws.com/public/python/cpython-3.14.4-x86_64-unknown-linux-gnu-pgo%2Blto-1110-20260429T1133.tar.zst
ARG PYTHON_STANDALONE_AMD64_SHA256=1988240030d33952727d828d5df699598bf6ef6d15dfd242dbc3192a413b81e4
ARG PYTHON_STANDALONE_ARM64_URL=https://astral-sh-dev-artifacts.s3.us-east-2.amazonaws.com/public/python/cpython-3.14.4-aarch64-unknown-linux-gnu-pgo%2Blto-1110-20260429T1133.tar.zst
ARG PYTHON_STANDALONE_ARM64_SHA256=77f5da4daceffc8c93a372b24aab57825cfbfb264061db142b6046446181f19e

[JacobCoffee]

lgtm, let me make sure security folks are happy