Deferring side effecting code in `_Py_Dealloc()`

Currently _Py_Dealloc() can call arbitrary code, and since _Py_Dealloc() can be called by any Py_DECREF() is means that Py_DECREF() can call arbitrary code. Py_DECREF() is everywhere, so it impairs our ability to reason about about the behavior of code.
This problem is not as severe as https://github.com/python/cpython/issues/97922, but is still worth fixing, especially as it will impair our ability to optimize traces for 3.12.

We can either make a Py_SAFE_DECREF() to be used internally, or change Py_DECREF() to defer all potentially side-effecting deallocation functions.

It is not clear which is the best option. Changing Py_DECREF() is simple, and certainly easy to reason about, but might delay deallocation of extension module objects for too long.

首先检查该 issue 中引用的 _Py_Dealloc() 和 Py_DECREF() 入口点，然后阅读 issue 97922 以了解相关背景。比较提议的 Py_SAFE_DECREF() 方案与直接修改 Py_DECREF() 本身的方案，包括对扩展模块对象释放的影响。完成的标准是选择并实现一个有充分依据的设计，并覆盖由此产生的释放行为。