[ISSUE #10987] Preserve offsets during correction query

[zjncs]

Which Issue(s) This PR Fixes

Fixes #10987

Brief Description

ConsumerOffsetManager.queryMinOffsetInAllGroup iterated the live offsetTable.keySet() view and removed matching groups while answering a correction-offset query. The iterator removal and removeConsumerOffset call permanently deleted consumer offsets as a read-side effect.

Copy the key set before filtering and remove matching keys only from that temporary set. The live offset table is now left unchanged while the query excludes the requested groups from its calculation.

How Did You Test This Change?

• Base SHA: $(git rev-parse develop).
• Confirmed current code assigned offsetTable.keySet() directly and called removeConsumerOffset during the query.
• git diff --check passed.
• Maven is unavailable in this environment, so the required test suite was not run; CI should validate.

Risk

Low; this removes an unintended destructive side effect from a read/query operation while preserving filtering behavior.

AI-assisted contribution; implementation and verification performed against current develop.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[RockteMQ-AI]

Summary

This PR fixes two related issues in the offset correction query path:

1. ConcurrentModificationException prevention: Wraps offsetTable.keySet() in new HashSet<>(...) to create a defensive copy before iterating. This prevents CME when entries are removed during iteration.

2. Incorrect offset deletion: Removes the removeConsumerOffset(topicAtGroup) call inside the correction loop, which was deleting offsets that should be preserved.

Both fixes are correct and address real bugs in the offset management logic.

LGTM.

---

Automated review by github-manager-bot