migrate to mail based update status update system

[hrideshmg]

This PR removes the current discord based status update system and migrates it to the new mail based system which relies on Root.

Pre-requisite PR: amfoss/root#154

Summary of changes:

• Removed the graphQL mutations as they are no longer used.
• Updated the models and fetch query to reflect the new refactored root syntax.
• Uses data from root to exclude members who have status updates suspended, logic for this can be found in feat: implement status update breaks root#154
• The consecutiveMiss attribute is used to find the strikes for the members (also accounts for status breaks), see above PR for more info.
• Removed redundant and dead code

[Copilot]

Pull Request Overview

This PR migrates from a Discord channel-based status update system to a mail-based system using Root's GraphQL API. The change simplifies the codebase by removing Discord message parsing and streak management logic, replacing it with direct data retrieval from Root.

• Replaces Discord channel monitoring with Root GraphQL queries for status update data
• Removes GraphQL mutation logic for streak management as it's now handled by Root
• Updates data models to reflect the new API schema with status information

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/tasks/status_update.rs	Major refactoring to use Root API instead of Discord message parsing
src/tasks/mod.rs	Renamed task struct from StatusUpdateCheck to StatusUpdateReport
src/ids.rs	Removed unused channel IDs for Discord-based status checking
src/graphql/queries.rs	Updated query to fetch member data with status information for specific dates
src/graphql/mutations.rs	Completely removed file as streak mutations are no longer needed
src/graphql/models.rs	Updated models to support new Root API schema with status tracking
src/graphql/mod.rs	Removed mutations module reference

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[ivinjabraham]

Is this up for review?

[hrideshmg]

Is this up for review?

Yep, I just have to make the Root PR for the miss streaks. Work is already done, just have to push.

[hrideshmg]

@ivinjabraham this is ready for review. Just tested it on a copy of the production database. Once we merge this and the prerequisite PR, we can fully move to the mail based system

[ivinjabraham]

LGTM