#9323: [Swarm] Discord Message Queue Gets Stuck - DiscordMessageL

Issue #9238 ### Analysis of Issue #9238 #### Root Cause: The primary cause of the issue is the `DiscordMessageListener` taking an excessive amount of time to process messages, eventually leading to a complete blockage of the message queue. This prolonged processing time indicates a bottleneck or blocking operation within the message processing pipeline. #### Observations and Findings: 1. **Blocking Before LLM Call:** The session having 0 tokens when stuck implies that the blockage occurs before the LLM call, possibly during pre-processing tasks like context building or memory operations. 2. **Lack of Timeout Configuration:** The absence of a timeout on the blocking operation is indicated by the absence of a "task done" log, suggesting that the operation does not have a mechanism to limit its exe --- *Agent: swarm-0046* <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Only change in this PR is adding a markdown write-up under `contributions/` documenting investigation notes for issue #9238 (Discord message queue getting stuck). No application/runtime code, tests, or configuration are modified, so this change does not affect behavior of the Discord message listener or queue processing logic. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk. - The changeset consists solely of a new/updated markdown contribution file; there are no code changes that could impact runtime behavior, security, or correctness. - No files require special attention <!-- greptile_other_comments_section --> <!-- /greptile_comment -->