Druid did not remove segments from middle manager after ingestion task failed

### Affected Version
0.22.1

### Description
**What happened?**
- Druid did not remove segments from middle manager after the ingestion task failed

Background
- For some reason, some Kafka ingestion tasks at some point failed. We saw InterruptedExceptions in the logs.
- We are thinking it is likely due to some overlord failure.
- The tasks reran and they auto recovered.

Question
- One of the ingestion task that failed may have created some realtime segments that got interrupted. Those segments did not get removed from middle manager.
- Is this behavior expected? If the tasks auto recovered, such stray segments should also have been deleted but they continued to stay on middle manager.

Begin with the middle manager's handling of failed Kafka ingestion tasks and the Overlord/task logs, especially the InterruptedException path. Confirm whether interrupted realtime segments are expected to be removed after recovery and document or reproduce the cleanup outcome; no file or test is identified in the issue.

Written by the indexing model from the issue text.