Is your feature request related to a problem? Please describe.

For hot ranges, we suggest tuning cluster level settings:

• kv.range_split.by_load_enabled
• kv.range_split.load_qps_threshold
• kv.range_merge.queue_enabled

However, these settings will have impact on all workloads across the cluster, whilst the hot ranges issue appears within individual databases/tables. From a blast radius perspective:

• We don’t want change these settings and impact a whole cluster at once.
• Different workloads (against different tables) might want these settings to be tuned differently.

This shows up in internal incidents as well: https://github.com/cockroachlabs/support/issues/1590.

Describe the solution you'd like

We want to be able to tweak these settings on a per-schema object level. We already have per-schema object configurations provided through zone configs; we could introduce new fields there. We could also audit other cluster settings that would benefit from the same treatment.

Jira issue: CRDB-10140
Epic: CRDB-26686