How does adding a WHERE clause filter on a non-selective field in a SOQL query on an LDV object cause full-table scans, and what design changes prevent this?