`tp_doc` switch from `PyObject_Malloc` to `PyMem_Malloc` is not backwards compatible

Bug report

In https://github.com/python/cpython/pull/114574 we switched a number of non-PyObject allocations from PyObject_Malloc to PyMem_Malloc, including tp_doc on PyHeapTypeObjects.

Unfortunately, this isn't backwards compatible because C-API extensions may allocate tp_doc contents, which are then freed by CPython in type_dealloc. For example, pybind11 allocates memory for the docstring using PyObject_MALLOC. This leads to crashes when using pybind11 in debug builds of Python 3.13: the allocation uses PyObject_MALLOC, but the memory is freed using PyMem_Free.

We should consider reverting the change to tp_doc and figure out a way to allocate the doc in a way that's both safe (in the free-threaded build) and doesn't break backwards compatibility (in the default build).

cc @erlend-aasland

Linked PRs

• gh-156990

Comienza con el cambio de asignación citado en PR 114574 y la ruta de liberación en Objects/typeobject.c; después revisa el PR vinculado gh-156990. Reproduce el caso de una extensión en una compilación de depuración usando un tp_doc asignado con PyObject_Malloc; se considera terminado cuando la asignación y la liberación siguen siendo compatibles para las extensiones existentes en ambos modos de compilación compatibles.