Ticket 589 seed file assign ta by criteria

[Naragod]

Proposed Changes

When developers set up MarkUs locally, the app fills itself with fake data (seed data) to allow local testing of without usage of real data. Previously, assignment A1 had students and grading rubrics without TAs assigned to any groups or criteria. This meant anyone wanting to test TA-related features such as the graders page, criteria-based grading, or TA workload views all had to be manually set up every time users reset their database.

This PR adds a new seed task that automatically:

• Assigns every TA to student groups for A1 using a round-robin (each TA gets an equal share)
• Turns on "assign graders to criteria" mode for A1
• Links each grading criterion to a TA
• Updates all the coverage/count caches which allows they UI to display correctly

Screenshots of your changes (if applicable)

Associated documentation repository pull request (if applicable)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)	X
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• I have updated the project documentation, if applicable.
  • This is required for new features.
• If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

• I have updated the project Changelog (this is required for all changes).
• I have verified that the pre-commit.ci checks have passed.
• I have verified that the CI tests have passed.
• I have reviewed the test coverage changes reported by Coveralls.
• I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[coveralls]

Pull Request Test Coverage Report for Build 23172746142

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 91.675%

---

Totals
Change from base Build 23091690132:	0.0%
Covered Lines:	45077
Relevant Lines:	48357

---

💛 - Coveralls