Smaller objects for the free-threading build using smaller integer types for refcount

The literature on reference counting for JVM and other GCs show that very few reference counts get to more than 7. This matches up with our stats that should the ratio of refcount ops to object allocations is about 6/7 to 1.

With that in mind, it would make sense to make the C ints used to represent refcounts smaller.
Instead of:

    uint32_t ob_ref_local;      // local reference count
    Py_ssize_t ob_ref_shared;   // shared (atomic) reference count

we can use:

    uint8_t ob_ref_local;      // local reference count
    uint32_t ob_ref_shared;   // shared (atomic) reference count

using 5 bytes instead of 12.

If ob_ref_local would overflow, we can atomically move some of that count into ob_ref_shared.

if (++op->ob_ref_local == 0) {
    atomic_add(&op->ob_ref_shared, 128);
    op->ob_ref_local = 128;
}

ob_ref_shared can use the same approach to saturation and immortality that the default build currently does.

Nenhum arquivo ou teste é nomeado. Comece pelas definições e usos de ob_ref_local e ob_ref_shared no build free-threading e, em seguida, rastreie o overflow da contagem de referências, as atualizações atômicas, a saturação e o comportamento de imortalidade. A tarefa estará concluída quando o layout menor funcionar sem alterar a correção da contagem de referências nem o comportamento de overflow declarado.