fix : added monotonic counters for reply_id and answer_id in CommunityManager

[tmdeveloper007]

Summary of What Has Been Done

Fixed the reply ID and answer ID generation in src/utils/community.py to use monotonic counters instead of length-based counting, preventing ID collisions after deletions.

Changes Made

• Added _reply_counters and _answer_counters dicts to CommunityManager.__init__
• Changed reply_to_discussion to use self._reply_counters for monotonically increasing reply IDs
• Changed answer_question to use self._answer_counters for monotonically increasing answer IDs

Previously, both methods used len(list) to generate IDs:

"reply_id": f"reply_{len(self.discussions[discussion_id]['replies'])}"
"answer_id": f"answer_{len(self.questions[question_id]['answers'])}"

This caused ID collisions when replies or answers were deleted, as the list length would shorten and subsequent IDs could collide with previously deleted entries.

Impact it Made

• Ensures reply and answer IDs are unique and monotonically increasing per discussion/question
• Prevents ID collisions if replies/answers are ever deleted
• Future-proofs the system for delete functionality

Note

Please assign this PR to the tmdeveloper007 account.

Closes #1329

[vercel]

@tmdeveloper007 is attempting to deploy a commit to the komalsony234-1530's projects Team on Vercel.

A member of the Team first needs to authorize it.