Supposedly lightweight tasks, we'll see

* Fix erroneous use in tests that didn't show until now

3.11.0+: Use the `--with-openssl-rpath' Configure option when possible

The options is available since 3.10.0+ (https://github.com/python/cpython/pull/24820)
but has no effect until 3.11.0 (cpython b9e9292d75)
and broken in MacOS until 3.12.2 (cpython cc13eabc7c),
we add downstream patches to fix that except for 3.11-dev where we disabled it

* Add graalpy-25.0.3

* CI: modified_scripts_build : fix GraalPy version detection

---------

Co-authored-by: Ivan Pozdeev <vano@mail.mipt.ru>

fixes stalling for 60s and failing if some past fault
has resulting in a stale lockfile being present

---------

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

GCC 15+ uses C23 by default
(https://www.phoronix.com/news/GCC-15-Default-C23)

fixes "error: static declaration of ‘sinpi’ follows non-static declaration"
fixes "error: cannot use keyword ‘false’ as enumeration constant"

* use OpenSSL 1.0 and 1.1 only from formulae

According to Miniforge README, they are only meant for interactive installation

* Keep bundled OpenSSL 3
There's no support for OpenSSL 4 yet

---------

Co-authored-by: native-api <2670332+native-api@users.noreply.github.com>
Co-authored-by: Ivan Pozdeev <vano@mail.mipt.ru>

* CI: add_version: correctly handle exceptions

exit code 1 is used as a signal that no new version is found -- so have to use a different exit code for unhandled exceptions

* CI: add_version: support prereleases for non-initial releases

They unexpectedly made a prerelease 3.14.5rc1

* clarify confusing error message

They unexpectedly made a prerelease 3.14.5rc1

exit code 1 is used as a signal that no new version is found -- so have to use a different exit code for unhandled exceptions

3.15.0b1 released means we need 3.16 support

Due to load peak at 0 minutes, it may fail to get a runner.
Github tries to allocate a runner for ~15 minutes.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

getting "no runner found" errors

* Add PyPy v7.3.22

The release blog entry is here:
https://pypy.org/posts/2026/04/pypy-v7322-release.html

* CI: Don't require openssl@1.1

Missing in macos-26 Homebrew, causing an error,
no longer required for any supported Pythons

---------

Co-authored-by: Ivan Pozdeev <vano@mail.mipt.ru>

Missing in macos-26 Homebrew, causing an error,
no longer required for any supported Pythons

The release blog entry is here:
https://pypy.org/posts/2026/04/pypy-v7322-release.html

Avoids O(N^2) complexity when `pyenv-latest` is called in a loop
for existing entries

the Github runner is out of beta

[no ci]

Co-authored-by: native-api <2670332+native-api@users.noreply.github.com>

this checks if "no acceptable C compiler found" is in the last 10 lines of the log, and asks if the user has correctly installed the build dependencies.

Bumps the github-actions group with 1 update: [actions/create-github-app-token](https://github.com/actions/create-github-app-token).


Updates `actions/create-github-app-token` from 2 to 3
- [Release notes](https://github.com/actions/create-github-app-token/releases)
- [Commits](https://github.com/actions/create-github-app-token/compare/v2...v3)

---
updated-dependencies:
- dependency-name: actions/create-github-app-token
  dependency-version: '3'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

[no ci]

Closes #3427
[no ci]