feat: availability page functionality

[KevinWu098]

Summary

1. Fully incorporates Login Modal into the availability page
2. Signed-in users can create and update availabilities
3. Guest users can be created and edit their availability (until they reload, or otherwise lose their current session)

Testing Plan

1. Create a meeting (example given in databaseUtils.server.ts) -- feel free to test dates/times other than the one I listed, but some values are hardcoded (start and end times), so ymmv
2. Go to /auth and create a user
3. Logout of account
4. Go to /availability/[YOUR_MEETING_ID_FROM_ABOVE]

Login Modal Flow

1. Select availability
2. Click save (cancel is not working, currently)
3. Auth Modal pops up

Authed User

1. Login with an account
2. Auth Modal closes
3. Availability saves
4. Confirm that availability is saved by refreshing the page (or check DB)

Guest User

1. Choose a guest name and click save
2. Modal closes
3. Availability saves
4. Confirm availability is saved by going to availabilityStore.ts and setting the value of guestSession.guestName to whatever name you choose above
5. Availability should render in (click on calendar to forcibly trigger rerender)

Future Followup

1. Currently, if a username has already been chosen, users cannot use that name in the login flow.

• For now, I've defaulted to this behavior allowing a guest to sign in again (load in their previous schedule) through the LoginModal
• As @MinhxNguyen7 suggested, we can offer users the ability to either load in their prior availability or to overwrite their existing availability

2. Cancel button

• The cancel button isn't working right now, which is possibly related to # 3
• Currently, when clicked, we grab the DB's availability and (hopefully) replace/bring back the pre-edit availability

3. Rendering the availability from the store

• For some reason, the calendar component does not render in the values from the store all at once, often only rendering in availabilities for the first column
• This requires a user input to forcibly rerender the component and display the current availabilities, which, to reiterate, are written to the store all at the same time (so why is it not rendered at the same time?)

[KevinWu098]

Note: Use some byte (0, 1) string in database instead of true, false

[KevinWu098]

note: add in guest stuff here, move group availability to followup

[MinhxNguyen7]

I think the deployment doesn't work because it's not up to date with what's on main

[seancfong]

Looks good to me. I'll go merge this in now to unblock other issues.

[seancfong]

@KevinWu098 Merging to main is blocked because of failing deployment. It might be because of the schema revert in 89a751c.

Can you change zotMeet.table to pgTable in src/lib/db/schema.ts? You can also look at the action log to see if anything else might be causing the issue.

[seancfong]

@MinhxNguyen7 Requesting review since I made a commit on this branch

[MinhxNguyen7]

Your merge looks good to me @seancfong. That's the extent of my review.

[MinhxNguyen7]

🎉