sql: use DeleteRange with MVCC range tombstone for schema GC

[erikgrinaker]

This is the cheap version of #70427.

We can keep the current schema GC system around, but instead of dropping a ClearRange we drop a DeleteRange with an MVCC range tombstone (requires #70415 first). It will then get cleaned up by MVCC GC at some point. This should only be done when a TBD experimental cluster setting and version gate is enabled, which it won't be by default. This will at least preserve MVCC guarantees, enabling incremental tenant backups and streaming cluster replication.

This will be ineffectual until we implement MVCC range tombstone GC in #70414, but we can get the plumbing in place at least. The cluster setting will be marked as experimental anyway, at least to begin with.

[postamar]

Duplicate of #70427

[erikgrinaker]

Is it though? This issue is essentially about calling DeleteRange instead of ClearRange, i.e. a simple change, while the other issue is about removing most of the SQL schema GC system entirely and using MVCC GC instead.

Of course, totally up to SQL schema how you want to do this, but I'd like to get some minimal fix in before stability to avoid non-MVCC operations across the board, to enable incremental tenant backups.