Manually deleted consuming segments

PR #8663 adds a new endpoint to recreate consuming segments which have been deleted manually by admins. Now this resume endpoint is used in pause/resume consumption in PR #8986
@mcvsubbu brought up a good point that we can block deleting consuming segments in segment deletion endpoint. If we do this, then periodic RealtimeSegmentValidationManager job - which ensures all partitions are properly consuming - can only fixes the issues that might happen in edge cases of commit protocol and not fix the user errors. This will simplify the code on the periodic job.

Start by reading the segment deletion endpoint and RealtimeSegmentValidationManager, along with PRs #8663 and #8986 for the consuming-segment resume and pause/resume behavior. Determine how manually deleted consuming segments are currently recreated and how deletion should be restricted. Done means user-triggered deletion is prevented where appropriate while the periodic job still handles commit-protocol edge cases.

Written by the indexing model from the issue text.