Separate response for comment and task status history

[Sujanadh]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

• Fixes Comments and Task History in Same Response #1390

Describe this PR

This PR refactors the end point task_history using raw sql returning separate response for comments in task and task status history.
We dont need separate comment get endpoint now.

Response

[
  {
    "id": 110,
    "project_id": 236,
    "task_id": 2350,
    "action": "RELEASED_FOR_MAPPING",
    "action_text": "Status changed from READY to LOCKED_FOR_MAPPING by: svcfmtm",
    "action_date": "2024-03-26T04:32:15.998587",
    "status": "LOCKED_FOR_MAPPING"
  },
  {
    "id": 111,
    "project_id": 236,
    "task_id": 2347,
    "action": "RELEASED_FOR_MAPPING",
    "action_text": "Status changed from READY to LOCKED_FOR_MAPPING by: svcfmtm",
    "action_date": "2024-03-26T04:32:20.254619",
    "status": "LOCKED_FOR_MAPPING"
  }
]

comments

[
  {
    "id": 112,
    "project_id": 236,
    "task_id": 2349,
    "action": "COMMENT",
    "action_text": "<p>this is test comment for task id 2349</p>",
    "action_date": "2024-03-26T04:33:41.524730",
    "status": null
  }
]

Checklist before requesting a review

• 📖 Read the FMTM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?