SQL tenants must not be allowed to perform manual range splits. This would allow them to create arbitrarily many ranges, instead of the maximum range count of a tenant being a function of the maximum data size offered to it.

The best way to do this might be to lock down all Admin KV requests in a follow-up change to #52094. I need to explore that and see if it's possible or if we need to support other admin kv requests.