fix(api): return 404 for non-existent report updates

[Neverask1121]

🛑 STOP: Assignment & File Scope Check

• I am assigned to this issue.
• I verified that this PR ONLY touches the required files.

📋 PR Summary & Link

• **Closes [BUG] updateReportStatus returns 500 instead of 404 for non-existent report IDs #2011 **

• Summary:

  • Fixed incorrect error handling in updateReportStatus().
  • Added handling for Supabase "no rows found" errors.
  • The endpoint now returns 404 Not Found when attempting to update a report that does not exist instead of returning a generic 500 Internal Server Error.

📸 Proof of Work (Screenshots / Logs)

Test Case 1: Existing Report

• Updated an existing report successfully.
• Received a successful response with HTTP 200.

Test Case 2: Non-Existent Report

• Attempted to update a report using an invalid/non-existent report ID.
• Verified that the API now returns HTTP 404 with the message:

{
  "error": "Report not found"
}

🏷️ PR Type

• 🐛 type: bug
• ✨ type: feature
• 📖 type: docs
• 🧪 type: testing
• 🔒 type: security
• ⚡ type: performance
• 🎨 type: design
• ♻️ type: refactor
• 🛠️ type: devops
• ♿ type: accessibility

✅ Checklist

• My PR has a linked issue (Closes #2011 )
• I have pulled the latest main and resolved any conflicts

[Neverask1121]

@dipexplorer Hello there, this is enough to merge and close the issue!
Because only some changes made the problem would be critical...

[github-actions]

🎉 Congratulations @Neverask1121! Your Pull Request "fix(api): return 404 for non-existent report updates" has been successfully merged by @dipexplorer.

Thank you for your valuable contribution to SahiDawa! 🇮🇳
If this was for GSSoC 2026, your work is officially merged and valid. Keep up the great work and feel free to claim other open issues. 🚀

Follow us on LinkedIn: https://www.linkedin.com/company/ratloopz/ to get shoutout