ci: update ffi-check for PyPy symbol mangling change

[davidhewitt]

As per pypy/binary-testing#55 (comment) this updates ffi-check to confirm that symbols are being resolved properly for PyPy ahead of the change in PyPy 3.12 to support abi3 by removing the special PyPy prefix from many functions.

I make this practical by forcing pyo3-ffi-check to resolve actual addresses of all functions and check they match the pypy headers.

[bschoenmaeckers]

LGTM!

[codspeed]

Merging this PR will not alter performance

✅ 141 untouched benchmarks
⏩ 6 skipped benchmarks¹

---

_{Comparing davidhewitt:pypy3.12-abi3 (7e50cbc) with main (a859d05)}

Footnotes

1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[mattip]

This probably needs an update. PyPy3.11 will keep the old names, PyPy3.12 will be using unmangled names for all the CPython limited API functions. You can see the latest CI run with PyPy3.12 at https://github.com/pypy/binary-testing/actions/runs/34744801359/job/103690612698

[mattip]

Wow. Sorry for the many many required changes.

[davidhewitt]

No worries; I think part of this is that PyO3 wasn't quite correctly mangling all the PyPy 3.11 symbols anyway, the more extensive checking applied here is catching existing flaws as well as preparing infrastructure to make sure we synchronise with PyPy 3.12 (and any future mangling changes).

[davidhewitt]

With #6411 and #6410 split out and merged this PR now is just a mechanical update of the pypy attributes; I'll set it to merge based on the prior approval when this PR originally looked like that (but with broken CI).

[mattip]

Thanks!