add #[track_caller] to all Py/Bound/Borrowed methods which panic

[davidhewitt]

While debugging pydantic/pydantic#9250 this morning, I realised it would be much more helpful if the panic message originated from the actual source location that attempted to construct the failed pointer, rather than deep in the guts of PyO3.

With this enabled, that reproduction actually panics with:

thread '<unnamed>' panicked at /home/david/dev/pydantic/pyo3/src/types/any.rs:2226:18:

which is in PyAnyMethods::dir - it turns out that __dir__ can indeed be fallible, so I'll open a separate issue for that now...

[codspeed-hq]

CodSpeed Performance Report

Merging #4098 will not alter performance

_{Comparing davidhewitt:track-caller (8bdbb00) with main (d42c00d)}

🎉 Hooray! pytest-codspeed just leveled up to 2.2.1!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

Summary

✅ 69 untouched benchmarks