check_versions.py: deprecate only if riscv64 wheels exist for target versions

[threexc]

Deprecate a package build only when each Python version we support has a corresponding wheel upstream. For example, the RISE registry currently builds for Python 3.12, 3.13, 3.14, and 3.14t. In this case, if an upstream wheel builds riscv64 for 3.12, 3.13, and 3.14, but not 3.14t, we should maintain the package workflow until 3.14t is also supported (or the package builds wheels for a future version of the RISE list).

Include a _self_test() function, providing a basic list of patterns to test against which can be expanded as wheel naming conventions evolve.

[justeph]

Do we really want to continue maintaining a package that does not ship one version of our build matrix? I think it's their responsibility. Let's suppose upstream decide to remove 3.12, I think we should not keep maintaining a build workflow for it. Same for 3.14t. Maybe the upstream project does not support free threaded at all.

[luhenry]

@justeph the issue here is hypothesis which doesn't ship a 314t upstream, so any other package that depends on hypothesis for testing (which some do) then it will not test on 314t specifically.

[threexc]

@justeph @luhenry it looks like hypothesis in particular may support threaded soon (for 3.15): HypothesisWorks/hypothesis#4851

Regardless, we should still have a course of action for when wheels don't exist for all of the version we're targeting. This will get a bit more difficult once 3.15 formally ships, since we'll probably need to build for 3.12, 3.13, 3.14, 3.14t, 3.15, and 3.15t.

Maybe we should consider trying to upstream threaded wheels (if it's simple) as an extension of our mandate to get projects building for riscv64?

See also: HypothesisWorks/hypothesis#4028 and HypothesisWorks/hypothesis#4451

[luhenry]

please do not merge just yet, I want to push #834 first. I shall be done in 15-20 min ideally done