* Count number of actually tracked objects, instead of trackable objects. This ensures that untracking tuples has the desired effect of reducing GC overhead* Do not track most untrackable tuples during creation. This prevents large numbers of small tuples causing execessive GCs.(cherry picked from commit0c01090)Co-authored-by: Mark Shannon <mark@hotpy.org>

…-140262 (GH-140447)* Count number of actually tracked objects, instead of trackable objects. This ensures that untracking tuples has the desired effect of reducing GC overhead* Do not track most untrackable tuples during creation. This prevents large numbers of small tuples causing execessive GCs.

This reverts parts of thepythonGH-140262 change.  The changes that affect thetuple untracking are left unchanged.  Revert the changes to thecalculation of the increment size, based on the "work_to_do" variable.This causes cyclic garbage to be collected more quickly.  Revert alsothe change to test_gc.py, which was done because the expected GCcollection was taking longer to happen.With the tuple untrack change, the performance regression as reported bybugpythonGH-139951 is still resolved (work_to_do changes are not required).