Make extent replacement idempotent
When clients lose connection with the Kusto server during
.replace extents in table commands they may end up retrying a command which succeeded, resulting in the data in the destination table being deleted instead of transferred. Adding a way for the client to specify something like ingestIfNotExists would resolve that issue. Alternatively, having an option to prevent the command from going through if there is no source data would also prevent the deletion.