cdc: locality_filter documentation issue

https://www.cockroachlabs.com/docs/v23.1/changefeeds-in-multi-region-deployments#run-a-changefeed-job-by-locality

```
When a node matching the locality filter takes part in the changefeed job, that node will read from the closest [replica](https://www.cockroachlabs.com/docs/v23.1/architecture/reads-and-writes-overview#architecture-replica). If the node is the leaseholder, or is itself a replica, it can read from itself. In the scenario where no replicas are available in the region of the assigned node, it may then read from a replica in a different region. As a result, you may want to consider [placing replicas](https://www.cockroachlabs.com/docs/v23.1/configure-replication-zones), including potentially [non-voting replicas](https://www.cockroachlabs.com/docs/v23.1/architecture/replication-layer#non-voting-replicas) that will have less impact on read latency, in the locality or region that you plan on pinning for changefeed job execution.
```

I'm not sure we actually can run rangefeeds against non-voter replicas. I think locality option is all about changefeed processor placement. But I think we would still establish rangefeed against lease holder (I might be wrong, so, need to verify it).

Jira issue: CRDB-31279