Add Resolved/Unresolved Functionality to Topics

[Misterurias]

📝 Context

• This PR introduces a resolved/unresolved feature for topics in NodeBB.
• The purpose is to allow users to mark a topic as resolved when a question is answered and unresolved when it requires further discussion.
• This improves thread management and makes it easier for users to find open/unanswered questions.

✅ Changes in the Codebase

• Added API endpoint to set resolved/unresolved status
  • Modified: src/routes/api.js
  • Added: PUT topics/:tid/resolved route (end of file)
• Added controller to handle resolved/unresolved status
  • Modified: src/controllers/topics.js
  • Added: setResolved() function to update the topic status (end of file)
• Updated API logic to modify database
  • Modified: src/api/topics.js
  • Added: setResolved() function to flip resolved boolean status in Redis (end of file)
• Updated Redis database schema to include resolved field
  • Modified: src/topics/create.js and public/openapi/components/schemas/TopicObject.yaml
  • Added resolved field (default is false) to topics data (beginning of file)
• Modified: test/topics.js
  • Added Unit tests
  • Added Integration tests
  • Tests for:
    • Setting a topic as resolved
    • Unsetting a topic (marking it as unresolved)
    • Ensuring the database updates correctly

[Ginka3]

Great work on adding the resolved/unresolved functionality! 🚀
Used the API endpoints and resolved states for marking topic as resolved branch already, no issues there. LGTM

[SubtoFelix]

The PR description is very well-defined. There are proper API designs and database schema updates that are persistent, queryable, and optimized. Additionally, there are appropriate units and integration tests that cover edge cases and ensure code quality and correctness. Overall, every features look great!

[sophiazhuu]

Amazing work!! Just ran through the test suite and it looks great. Excellent code changes that are clear, uniform, and correct. Tests are thorough and successful! LGTM :)