Schedule Review Table Data Fetch

[hujoseph99]

Ticket link

Closes #162

Implementation description

• Created new endpoint shiftsWithSignupsAndVolunteersByPosting
• This is a draft PR, still have to add the front end data-fetching

Steps to test

1. Populate database as in this Built out shift signup endpoints #90
2. Add skills and branches for the user with the following queries: `

• insert into skills values (1, "test skill");
• insert into branches values (1, "test branch");
• insert into "_SkillToVolunteer" values (1, 1);
• insert into "_BranchToVolunteer" values (1, 1);

3. Test the query to see if it works as expected in :5000/graphql
4. Go to frontend route /admin/scheduleTableDemo to see demo of query
5. Input appropriate posting ID, user ID, and signup status for testing

Note that the queries createShifts, createShiftSignups, and updateShiftSignup will likely be useful for creating shifts and signing up to them.

What should reviewers focus on?

• The reviewer should focus on checking to see if the table is populated as expected with the different filters for posting ID, user ID, and signup status.

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

[github-actions]

Visit the preview URL for this PR (updated for commit 7c7b8e3):

https://sistering-dev--pr259-joseph-schedule-revi-rnqlxck9.web.app

_{(expires Fri, 29 Apr 2022 00:42:39 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

[LenaNguyen]

looking good, the main changes have to do with 1) removing skills + branches from the response and 2) add another where filter to the prisma query for userId and signupStatus

[LenaNguyen]

No action needed on this pr but we should probably store user emails in the db so we don't have to make a call to firebase every time. We'll do this in the future!

[LenaNguyen]

remember to run yarn fix to address linter errors :)

[LenaNguyen]

Thanks for incorporating all the changes! So glad to have this merged in :))