kvserver: warn about a quiesced leader not leaseholder range

In #101885 we saw a quiesced range that was in the state leader not leaseholer. This causes a number of problems as it is not a well-supported state, and will not "self-recover" until the range is externally written to.

We should add a big warning (or assertion) when the replicate queue detects this state. If it can detect it in a "race-free" way we can fatal, but otherwise it should simply log loudly.

Jira issue: CRDB-27182