fix(comments): explicitly return limbo status of comment

[edward-ly]

• Resolves: [Bug]: Comment still shows after being deleted until page refresh #55121

Summary

Adds an explicit (rather than implicit) return statement in the checkForId function. Otherwise, it will return undefined regardless of whether the comment is in limbo or not, causing comments in limbo to always mistakenly appear.

Before	After

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

[edward-ly]

/backport to stable32

[edward-ly]

/backport to stable31

[edward-ly]

/compile

[szaimen]

🐘

[backportbot]

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/55275/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 8858ba12 6f7b3b39

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/55275/stable31

Error: Failed to push branch backport/55275/stable31: remote: {"auth_status":"auth_error","body":"Invalid username or token. Password authentication is not supported for Git operations."}
fatal: Authentication failed for 'https://github.com/nextcloud/server.git/'

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.