fix: timesheet daily rejection reason propagated to new (day, project) timesheet pair

[robinroy03]

Description

timesheet daily rejection reason propagated to new (day, project) timesheet pair

Relevant Technical Choices

1. added a check for it every time a timesheet is submitted

Testing Instructions

#1741 (comment)

Checklist

• I have carefully reviewed the code before submitting it for review.
• This code is adequately covered by unit tests to validate its functionality.
• I have conducted thorough testing to ensure it functions as intended.
• A member of the QA team has reviewed and tested this PR (To be checked by QA or code reviewer)

Fixes ##1741 (comment)

[Copilot]

Pull request overview

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Propagates a rejected day’s rejection reason to newly created timesheets on the same day (e.g., a new project entry created after the day was already rejected).

Changes:

• Add per-day rejection aggregation and a propagation map during weekly status updates.
• Apply propagated day-level rejection status/reason when updating each timesheet.
• Add a unit test covering creation of a new same-day/project timesheet after rejection.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
next_pms/timesheet/api/utils.py	Computes and applies day-level rejection propagation during weekly status updates
next_pms/tests/timesheet/api/test_timesheet_rejection_reason.py	Adds fixture data + a test ensuring same-day new timesheet inherits rejection

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.