fix pypy tests on windows

[davidhewitt]

Change Summary

Avoids the crash in windows pypy PGO builds.

Related issue number

N/A

Checklist

• Unit tests for the changes exist
• Documentation reflects the changes where applicable
• Pydantic tests pass with this pydantic-core (except for expected changes)
• My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

[codspeed-hq]

CodSpeed Performance Report

Merging #757 will degrade performances by 61.16%

_{Comparing dh/fix-windows-pypy-tests (9ec612c) with main (a27b34e)}

Summary

❌ 2 regressions
✅ 124 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	dh/fix-windows-pypy-tests	Change
❌	test_definition_model_core	1.8 ms	4.7 ms	-61.16%
❌	test_field_function_validator	795.4 µs	1,833.3 µs	-56.62%

[davidhewitt]

Benchmark "regressions" are expected because I've made these recurse deeper (they now run all the way to our hard-coded recursion limit).

[codecov]

Codecov Report

Merging #757 (9ec612c) into main (0b31711) will decrease coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #757      +/-   ##
==========================================
- Coverage   93.65%   93.64%   -0.01%     
==========================================
  Files          99       99              
  Lines       13938    13942       +4     
  Branches       25       25              
==========================================
+ Hits        13053    13056       +3     
- Misses        879      880       +1     
  Partials        6        6              

Impacted Files	Coverage Δ
src/recursion_guard.rs	95.65% <ø> (ø)

... and 2 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b31711...9ec612c. Read the comment docs.