Clone table should optionally allow specifying a range to clone

**Is your feature request related to a problem? Please describe.**
Cloning a table is overkill if a small subset of the table is all that needs to be cloned. If the need to clone is for a small fragment of data it produces a large amount of GC overhead that is not necessary when cleaning up the clone.

**Describe the solution you'd like**
Adding an optional range to the clone table operation would allow a subset of the table to be cloned. This would limit the GC overhead to be only the files relevant to the clone.