Add _DuringGC functions for tp_traverse

Feature or enhancement

As seen in https://discuss.python.org/t/adding-c-api-for-use-in-tp-traverse/105331/13 and https://github.com/capi-workgroup/decisions/issues/95:

There are newly documented restrictions on tp_traverse:

The traversal function must not have any side effects. It must not modify the reference counts of any Python objects nor create or destroy any Python objects.

But, whether a C-API function modifies some reference count is an implementation detail that we can change at any time. Core devs can add logging, an audit event, or a warning, to virtually any function.
This implies that you can't safely use any C API function in tp_traverse, unless it guarantees that it has no side effects.

I propose to add such side-effect-free versions of some functions useful in tp_traverse, with a _DuringGC suffix -- namely:

• PyObject_GetTypeData_DuringGC
• PyObject_GetItemData_DuringGC
• PyType_GetModuleState_DuringGC
• PyModule_GetState_DuringGC
• PyModule_GetToken_DuringGC
• PyType_GetBaseByToken_DuringGC
• PyType_GetModule_DuringGC
• PyType_GetModuleByToken_DuringGC

Compared to their non-suffixed variants, the main difference is that we promise that these will remain safe to use in tp_traverse. The other differences are that these functions cannot fail, and (where applicable) they return borrowed references rather than strong ones.

Also, Py_VISIT, Py_SIZE, PyObject_VisitManagedDict as well as the visitproc that Python passes to tp_traverse will be documented to work like this.
[edit] I'll also include a few ones useful in these: PyObject_TypeCheck, PyType_IsSubtype, PyType_HasFeature, Py{<type>}_Check, Py{<type>}_CheckExact.

Users that call any _DuringGC function (including some type's tp_traverse) must manually must ensure that the type, MRO, and layout of any argument doesn't concurrently change. That means only calling them from tp_traverse.

Linked PRs

• gh-145925

Comece lendo a discussão vinculada sobre a C-API, a issue 95 de decisões e o PR gh-145925. Revise as funções _DuringGC listadas e as APIs relacionadas Py_VISIT, Py_SIZE, visitproc e de verificação de tipos. Considera-se concluído quando as APIs propostas sem efeitos colaterais e suas garantias de segurança para tp_traverse estiverem implementadas e documentadas.