Add slot descriptions, matcher randomness

[smartspot2]

Closes #466.

Matcher slots currently have no special metadata that coordinators can use to indicate special sections with---this information needs to be communicated to mentors separately. Adding a description to slots allows for this metadata to be embedded within the matcher, so mentors can see whether sections have any special tags (ex. NPE, affinity section, etc.) prior to filling availability.

Secondly, this PR also adds some randomness to the matcher algorithm, randomly shuffling the lists of mentors/slots/preferences so that tiebreaks happen approximately uniformly.

[cypress]

csm_web    Run #417

Run Properties:   Passed #417  •  01fa6f4332: Add slot descriptions, matcher randomness (#480)

Project	csm_web
Branch Review	master
Run status	Passed #417
Run duration	02m 18s
Commit	01fa6f4332: Add slot descriptions, matcher randomness (#480)
Committer	Alec Li
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	84
View all changes introduced in this branch ↗︎

[edwardneo]

Some minor things. I'm not sure which should be addressed in this PR or another PR.

• The precommit check is failing.
• It would be nice if the mentor side of the matcher had the descriptions on the tiles instead of only visible if you click on the tile -- otherwise, mentors have to click through the tiles to find the description. Or some other visual indicator of a description.
• The save button on the section edit page is always gray -- I think it should be green.
• The bulk editing feature on the section edit page only edits capacity and description, not section time. Should it edit section time?

[isabellaalps]

note: this PR should be prioritized over calendar as we need the description changes to be merged in before elaine and i make too much progress on the affinity section pop-up

+1 to edward's comments

[smartspot2]

Newest changes should resolve the aforementioned comments:

• Description is now displayed on the calendar event
  • I currently have it implemented where the description is displayed in parentheses on the same line as the event time; this is so that in most cases, the description will be visible, even if the event is 30 minutes long. If the schedule time or description text becomes too long, it'll overflow and get cut off, but that's just something we have to deal with regardless.
  • In the mentor view, this does mean that the preference number is more likely to get pushed out of the bounding box of the event, but again we'd have this issue regardless of the description if the event is 30 minutes long.
  • Not sure if there are any opinions on this; a more robust solution would be to have a larger bounding box on hover, though this would take more work, and I'm not sure if it's completely worth it at this point.
• Save button is now styled with primary-btn
• Bulk editing has now been fixed to also work with section times (this was probably missed in the initial implementation)

Regarding the pre-commit check, this is a more fundamental issue with the pylint configuration; it seems very weird that it's only failing for the fields in the DateTimeField models (and other similar time-related models), but after an update to pylint-django, it seems to have gone away? I've created #521 for that dependency update.

For now, we can just ignore the pre-commit failures in this PR, and #521 can be merged into master first if we want to maintain the passing CI on master.

[isabellaalps]

looks good to me :) ty Alec

[ElaineShu0312]

excellent work alec

[ElaineShu0312]

excellent work alec

[edwardneo]

Ok LGTM! I'll put more QOL feedback on another issue for someone to one day implement...