Avoid double checking `tp_as_number`, `tp_as_sequence` and `tp_as_mapping`

Feature or enhancement

The PyTypeObject fields tp_as_number, tp_as_sequence and tp_as_mapping can be set to NULL
which means that any code that wants to access a field in those structs needs to first check for NULL.
e.g. checking if an object is a sequence:
if (Py_TYPE(s)->tp_as_mapping && Py_TYPE(s)->tp_as_mapping->mp_length) {

this is ugly, a bit error prone and slower than necessary.
Instead, during PyType_Ready, any of these fields that are NULL should be made to pointer to a struct full of NULLs.
This would remove the need for the extra check:
if (Py_TYPE(s)->tp_as_mapping->mp_length) {
since we would be guaranteed that Py_TYPE(s)->tp_as_mapping is never NULL.

Immutable types can all share common constant structs, so this should use very little extra memory.

Linked PRs

• gh-149317
• gh-149476

从 PyType_Ready 开始，跟踪对 tp_as_number、tp_as_sequence 和 tp_as_mapping 的处理，然后检查 issue 中描述的访问模式。当 NULL 槽位能够在无需额外检查的情况下，通过所有元素均为 NULL 的共享结构体安全表示，并且相关 CPython 测试通过时，即表示完成。