When implementing the projection pushdown into the KV (#82323), at least initially, we won't support SKIP LOCKED waiting policy. The difficulty with that feature is that it uses roachpb.ResponseKeyIterate function over the keys that are included into the BatchResponse. However, with COL_BATCH_RESPONSE format, we don't have an easy way to access (nor to reconstruct) the original key because we only send the "needed" columns.

For a similar reason (we need to decode keys in acquireUnreplicatedLocksOnKeys), we won't support any lock strength other than lock.None.

Jira issue: CRDB-22064