[Preferences] Admin-Account API Endpoints

[rbassot]

Parent Epic: #5

Description: Administrator-facing frontend-backend API HTTP endpoints. This is from the perspective of the administrator.

Includes:

View 1: - GET /preferences/{year-semester} --> List all active constraints and preferences for all professors for a given semester or year. Should include profs that haven’t submitted a preferences form yet, but are expected to. {year-semester} is in the form of a 6-digit string, where the last two digits mark the starting month of the respective semester.

• GET api/preferences/{professor-id} --> List active constraints/preferences for a single professor. Should include profs that haven’t entered yet but are expected to.

View 2:

• POST api/preferences/{professor-id} --> Allows for manually editing of a specific professor's hard constraints that they have specified in their preferences form (I believe this functionality should not differentiate b/w soft/hard constraints, and instead handle changes to either in the same way). We do not need to edit professor soft constraint/preferences because algorithm decides on importance.

AC:

• Admin user is able to retrieve a table of teacher preferences entries in the JSON body of a response, which includes not yet submitted records.
• Admin can manually edit a specific preferences record in the database.

[rbassot]

First pass of these endpoints are complete and working. A full test suite will be completed prior to entering the PR phase.