Handle sharding key for loose_foreign_keys_deleted_records
## Problem
`loose_foreign_keys_deleted_records` needs a sharding key.
* If there is data relevant to an org in this table, and if Org Mover doesn't move it, then the deletions won't be performed after the move, and some data will be orphaned in the destination cell. Org Mover can only (efficiently) move PG data that has a sharding key.
issue