Add "sections" aggregate endpoint to professor endpoint

[jpahm]

Currently, it can be inconvenient and overcomplicated for our end users to perform some common aggregate operations such as getting all of a professor's sections.

As such, we should add the following endpoints which immediately aggregate and return matching professor's sections:

• Query based: GET /professor/sections (allows for querying like the base professor endpoint)
• ID specific: GET /professor/{professorId}/sections (gets sections only for a specific professor)

[mikehquan19]

I'd like to work on this so that all the endpoints tasks can be taken care of before new tasks pump out.

[jpahm]

I'd like to work on this so that all the endpoints tasks can be taken care of before new tasks pump out.

That would be wonderful, thank you! New tasks are mainly going to be oriented around unit testing the tools (I'll be breaking up that big L3 task in the todo list) so they shouldn't interfere with the API too much.

In any case, this is all yours!

[mikehquan19]

Hi @jpahm , I finally finished this task. Now I can move on and start working on the tasks of writing tests haha.

Thank you.