Evaluate whether any additional garbage collection stats would be useful

[fallwith]

With Ruby 3.3, the GC.stat hash has 31 keys. As of agent version 9.6.0, we report on 5 of these. Is there any value in reporting on any of the other 26?

NOTE: here are lists of keys for each currently supported Ruby version

2.4, 2.5, 2.6

• count
• heap_allocated_pages
• heap_sorted_length
• heap_allocatable_pages
• heap_available_slots
• heap_live_slots
• heap_free_slots
• heap_final_slots
• heap_marked_slots
• heap_eden_pages
• heap_tomb_pages
• total_allocated_pages
• total_freed_pages
• total_allocated_objects
• total_freed_objects
• malloc_increase_bytes
• malloc_increase_bytes_limit
• minor_gc_count
• major_gc_count
• remembered_wb_unprotected_objects
• remembered_wb_unprotected_objects_limit
• old_objects
• old_objects_limit
• oldmalloc_increase_bytes
• oldmalloc_increase_bytes_limit

2.7

• (all from the previous list)
• compact_count

3.0

• (all from the previous list)
• read_barrier_faults
• total_moved_objects

3.1, 3.2

• (all from the previous list)
• time

3.3

• (all from the previous list)
• marking_time
• sweeping_time

[workato-integration]

https://new-relic.atlassian.net/browse/NR-181026

[fallwith]

In addition to exploring the other GC.stats key/value pairs, we can also explore the other GC methods beyond stats to see if there's anything there we want to consider.