feat(videos): integration fixes for video appointment upload flow

[connordoman]

Welcome to PrivacyPal! 👋

Fixes: #357
Depends on #473

Description of the change:

Naturally, this PR grew to be annoyingly large.

This PR addresses many small to medium aspects of the user path for uploading a video to an appointment.

Some stand out changes are:

• dummy-authenticator now checks the database for credentials (aligns db and basic auth. db provider would be a more robust solution)
• Adds hashed passwords in user.properties.json in order for said auth to work
• appointment list in dashboard features links to appointments
• basic <AppointmentViewer /> component that acts as a stand-in for the real feature
• the viewer links to /upload?id=${appointmentId} and will raise 404 if the user is not authorized and/or the wrong or no id is specified
• /upload/status uses this id as well (+ request filtering)
• /upload/review uses this id as well (+ request filtering)
• All filtering happens server-side with RSC + actions.ts
• Failed uploads at /review return the user to the appropriate /upload page
• Successful uploads return the user to the relevant appointment (where the video would be viewable in a list)
• Server Action to query users by email
• Server Action to query users without returning their password
• Server Action to get a professional's appointment
• Server Action to get a client's appointment
• Server Action to check if a user is part of a given appointment
• probably some more stuff

Sorry for such a large PR. Some of these could have been on their own.

Also, smoketest is outdated, so thoroughly testing this feature set was challenging. I suspect it will work but thoroughly investigating is not worth it until new video processing has been implemented.

Motivation for the change:

Integration and cohesiveness

[tthvo]

@nganphan123 @linhnnk ping.

[connordoman]

@nganphan123 @linhnnk piiiing

[nganphan123]

There will be conflicts with this PR #406 when either is merged. We should consider which one to merge first to minimize the conflict fix.

[nganphan123]

I tested the app, everything works for me. Nice work!
I tried uploading video but it said no appointment id found. Does this PR include uploading video flow?

[connordoman]

I tested the app, everything works for me. Nice work! I tried uploading video but it said no appointment id found. Does this PR include uploading video flow?

The flow that works is

1. pro creates appointment
2. user finds appointment on dashboard
3. user clicks "upload video" from appointment page
4. this passes relevant data to /upload
5. flow continues with data being passed across routes until processed/declined

[MyStackOverflows]

Yeah took me a bit because I didn't realize I had to re-migrate the database (duh) but after testing I get to the same point as Ngan, video upload says "no appointment id provided"

[MyStackOverflows]

trying to build these changes and getting this, did the db schema/column names change?

[connordoman]

trying to build these changes and getting this, did the db schema/column names change?

It did. Fixed this but can't continue till Basic auth is merged

[MyStackOverflows]

It did. Fixed this but can't continue till Basic auth is merged

could that db change be why my attempts at creating appointments on #426 are failing? if so (since the actual auth part of the PR works) we can merge it and then work on this @connordoman

[github-actions]

This PR/issue depends on:

• fix(appt): add enum check for createAppointment #473
  By Dependent Issues (🤖). Happy coding!

[tthvo]

Hey team @COSC-499-W2023/team-1, @connordoman and I had a discussion on this and we agreed that it would better to split this PR into smaller ones.

Please prioritize reviewing #402 and #395 for wrap up appointment-related tasks.