Alternative for #8697

When sending a shard snapshot transfer to an existing shard, extra headroom is needed on the receiver. Specifically, the snapshot is first downloaded and then replaces the existing data. It means that we need double the size of a shard in terms of disk space.

This is a blocker on some customer deployments that have very large shards. And we'd like to start enabling snapshot transfer by default everywhere because it has better performance characteristics.

This PR adjusts the shard snapshot recovery process. It now clears the target shard and then downloads the snapshot. This is safe because the shard transfer itself marks the shard as dead, and so it will not be used in reads. Clearing first prevents needing the headroom.

All Submissions:

• Contributions should target the dev branch. Did you create your branch from dev?
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
3. Have you checked your code using cargo clippy --workspace --all-features command?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?