[Team's Response Phase] Synchronising issue that has been responded fails to fetch the submitted response

**Describe the bug**

After a team member has submitted a response, the synchronisation fails to update the new response, and instead removes any element below the main bug-report element. Pressing the `<` at the top to return to the main list and reopening the issue fixes this.

**To Reproduce**
Steps to reproduce the behavior:

1. Go to an issue that has not been addressed
2. Wait for another member of the team to submit a response
3. Wait for auto-sync or manually sync by pressing the "Sync" button on top
4. Observe missing response below

**Expected behavior**
The response below should be populated with the newly submitted response.

**Screenshots**

This is the current state where there is yet to be a response:


After another team member has submitted a response, synchronising the page with the "Sync" button results in no response below:

*note the scrollbar is at the end*


**Desktop (please complete the following information):**

- OS: NixOS 24.11.20240906.574d1ea (Vicuna) x86_64 (Kernel: 6.6.49)
- Browser: Brave 1.69.153 Chromium: 128.0.6613.85 (Official Build) (64-bit)

**Additional context**
This is for the "Team's Response Phase" PE segment of Catcher.

Start by reproducing the issue in CATcher's Team's Response Phase: open an unaddressed issue, submit a response from another team member, then use auto-sync or the Sync button. Trace the synchronization flow from the main issue view and verify that the newly submitted response appears without removing content below the main bug-report element.

Written by the indexing model from the issue text.