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() 本身的作法，包括對擴充模組物件解除配置的影響。完成的標準是選擇並實作一個有充分依據的設計，並涵蓋因此產生的解除配置行為。