Leave tracking from amD

[naveensrinivas282]

This PR

• creates a table Leave for
  • mutation mark_ leave
  • query leave_count
• add discord_id optional param for Member object so amD can query using discord_id itself
  These are currently meant only to be accessed by amD for marking and fetching leaves

[naveensrinivas282]

@hrideshmg Could you review this please ?

[Copilot]

Pull request overview

This PR introduces leave tracking functionality to support the amD Discord bot by creating a Leave table in the database and adding corresponding GraphQL mutation and query operations. The changes enable tracking member leaves with approval workflows and querying leave counts within date ranges.

Changes:

• Created a Leave database table with foreign key references to Member via discord_id, including constraints for leave approval validation
• Added mark_leave mutation to record new leave entries with discord_id, reason, duration, and optional approver
• Added leave_count query method to Member type for calculating total leave duration within a date range
• Extended the member query to accept discord_id as an optional parameter alongside existing member_id and email options

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 14 comments.

File	Description
migrations/20260214152404_create_leave_table.sql	Creates Leave table schema with foreign keys, defaults, and constraints including self-approval prevention
src/models/attendance.rs	Defines MarkLeaveInput, MarkLeaveOutput, and LeaveCountOutput structs for GraphQL API
src/graphql/mutations/attendance_mutations.rs	Implements mark_leave mutation to insert leave records with current timestamp
src/graphql/queries/member_queries.rs	Adds discord_id parameter to member query and implements leave_count resolver on Member type

---

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