Tracking: deprecate range tombstone

[hzxa21]

Given that we have introduced table watermark in #13148 and have all executors switched to use table watermark to clean up storage states, it is time to gradually deprecate the general-purpose range delete support via range tombstone in storage because it has deeply invaded in the read/write/compaction path of storage and increased the maintenance burden.

• Deprecate range tombstone in the write path (refactor(storage): remove writing delete ranges in flush #14776)
• Expose per table vnode watermark via SQL. User can make sure per table vnode watermark exists in all relevant state tables before upgrading to the future release version, where range tombstone is completely deprecated (feat(frontend): support system table to query storage table watermark #15344)
• Deprecate range tombstone in compaction refactor(storage): remove reading range tombstone in read path and compaction #15613
• Review executor read pattern and deprecate range tombstone in the read path. refactor(storage): remove reading range tombstone in read path and compaction #15613