[FRONTEND] Refactor table on bookings view

[bcho892]

Is your feature request related to a problem? Please describe. Redesign bookings view to only show important information (name, dietary requirements), make the dates go across instead of down - allow them to click on the members for more details.

The original document that the admins used on the google sheet was like follows:

|--------------------Date1------------------|------------------Date2-------------------| |---------Name-------- |-----Allergies-----|---------Name-------- |-----Allergies---- | |-------asdasdda-------|----asddsasdd----|-------asdasdda-------|---asddsasddds--|

It is probably worth creating a "new" component for this because a lot of the functionality is not shared between the original Table component.

BEFORE MERGING

• [ ] Storybooks created where possible
• [ ] Tested with nock if data fetching
• [ ] Tests written for critical interactions
• [ ] PR Reviewed (For non-trivial changes)
• [ ] Changes tested after rebasing on master or merging in master (hint: git fetch origin master:master, then git rebase master or git merge master)
• [ ] All required PR checks passing