Summary

PyBaseException uses the default no-op Traverse::clear. An owned exception whose cause points to itself can remain alive after the collector untracks it. The generated one-field wrapper forwards clear through MaybeTraverse::try_clear, but forwarding alone does not break the cycle.

This limitation predates the owned exception payload construction change. The existing weakref regression checks traversal and weakref invalidation; it does not prove that the exception payload is destroyed.

Required changes

• Implement base exception payload clearing in crates/vm/src/exceptions.rs so GC can break cyclic references safely.
• Preserve the generated wrapper clear forwarding in crates/derive-impl/src/pyclass.rs.
• Add regression coverage in the VM GC tests that observes actual payload destruction, not only weakref invalidation. Include an owned exception with a self-cause cycle.

Acceptance criteria

• After external references are dropped and GC runs, the self-cause cycle is broken and the exception payload is destroyed.
• The regression test fails when base payload clearing is a no-op and passes with the repair.
• Existing exception construction and GC tests continue to pass.

Requested by @JMLX42.

Related pull request: #9734
Review thread: #9734 (comment)