Currently range tombstone GC takes readwrite latches for range tombstones it tries to collect. This is usually broad as range tombstones are used to delete whole ranges.

Once latchless GC change lands (#83213), we can optimize range key GC requests to only get read latches to preserve range boundaries for the same of MVCC stats calculations, but don't prevent reads.

Jira issue: CRDB-17743

Epic CRDB-2624