feat: add Statuses table migration

[vindyakodithuwakku02]

Added new Statuses table to track maintenance issue progress updates.
Includes relations to Issues and Users, with ENUM status field and performance indexes.
Successfully migrated and tested using Docker Postgres (fixpoint_db).

[Copilot]

Pull request overview

Adds a new database migration to introduce a Statuses table for tracking maintenance issue progress updates, linking updates to both Issues and Users.

Changes:

• Create Statuses table with FK relations to Issues and Users, plus description, optional image_url, and status_type ENUM.
• Add indexes on issue_id and user_id to support common query patterns.

Comments suppressed due to low confidence (1)

src/database/migrations/20251027183315-create-statuses-table.js:64

• status_type is created with Sequelize.ENUM(...), which creates a PostgreSQL enum type (typically named like enum_Statuses_status_type). down() currently drops only the table, leaving the enum type behind; rolling back and re-running the migration can fail because the enum type already exists. Please update down() to also drop the generated enum type (similar to how other migrations drop enum types).

  async down(queryInterface, Sequelize) {
    await queryInterface.dropTable('Statuses');
  }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This migration is the only one in the repo using an ESM export default and a .js extension. With the project configured as "type": "module" and sequelize-cli driven by a CommonJS .sequelizerc, sequelize-cli will typically require() migrations; requiring an ESM .js file will throw ERR_REQUIRE_ESM. Align this file with the existing migrations (e.g., use .cjs and module.exports = { up, down }).

Suggested change

	export default {
	module.exports = {