feat: create scheduling crud endpoints

[annechung]

Notion ticket link

Ticket Name

Implementation description

• GET/POST/PUT/DELETE endpoints for the scheduling model

Steps to test

1. Create user and donor rows in their respective tables.
2. Send requests to http://localhost:5000/scheduling and test out functionality!

Sample JSON for creating a scheduling entry (POST):

{
    "donorId": 1,
    "category": "Tea and coffee",
    "quantity": 3,
    "pickupLocation": "anywhere",
    "startTime": "2020-10-13",
    "endTime": "2020-10-14",
    "status": "Pending",
    "volunteersNeeded": 0
}

What should reviewers focus on?

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[Shehryar21]

First Pass. I havent tested it through postman yet, but will do once the changes are implemented. Good job on it though! Also the tests are failing in CI. Can you take a look at that?

[Shehryar21]

Default value should be Approved. Can we add that in? We would not need @AllowNull(false) then? This would require some changes in the functions as well.

[linnall]

Wouldn't the default value be Pending since when a schedule is created, it then has to be approved by an admin?

[Shehryar21]

Can we change this to category instead? Please look at the following product spec: https://www.notion.so/uwblueprintexecs/Creating-Info-for-Food-Donor-Dropoff-60826a71e0114f81a837e6933922a4dd#e85ab7e5abbc42e09ac8327001f9c65d for different categories. I guess we could still keep it as a string instead of Enum, and the Frontend would only provide those listed options in the dropdown. In that case, only need to change the name.

[annechung]

Think we've addressed all comments! @Shehryar21

[hanlinc27]

haven't tested locally yet but looks good!