mechanism to control python-build-standalone "release" version

[cburroughs]

Is your feature request related to a problem? Please describe.

The python build standalone project provides calendar versioned "releases" that are separate from the underlying CPython version. For example https://github.com/indygreg/python-build-standalone/releases/tag/20240726

One can control the version of CPython used with interpreter constraints, but there is not a way to specify the 'release'. This would be useful for:

• Ensuring an exact version is used everywhere consistency.
• Ensuring a version greater than some bugfix is used.

Describe the solution you'd like

A way to specify the release. I suspect it is adequate for it to be global (that is using a differnt release for python 3.10 and 3.11 is excessively niche)

Describe alternatives you've considered

One can limit the known version,:

"'3.9.16|linux_arm64|75f3d10ae8933e17bf27e8572466ff8a1e7792f521d33acba578cc8a25d82e0b|24540128|https://github.com/indygreg/python-build-standalone/releases/download/20221220/cpython-3.9.16%2B20221220-aarch64-unknown-linux-gnu-install_only.tar.gz',"

But that's a lot of duplicate toil.