Wire up intake frontend to backend

[YashK2005]

This PR completes the intake forms end-to-end. Once the user creates an account and logs in they are taken to the participant or volunteer intake forms depending their role. Once they fill out the intake form, data is sent to the backend, processed, and stored in the db tables.

Things to do next / questions:

• what should we do after the intake form is submitted (like what should show up next in the UI) - right now after they log in they will just see the intake form again
• we must complete the rankings forms --> this requires mostly backend but also some frontend like making sure some of the options are fetched from the backend (for the experiences) rather than hardcoded. I will rebase our rankings branch onto this one and work on this

• also should have some frontend gating by role - eg. if i am a volunteer i can still go to the /participant/intake form and fill that out. we should block this
• i don't think we've done the secondary screening for volunteers yet so that should be done (we can probably do this during the fall term)

Notion ticket link

Ticket Name

Implementation description

Steps to test

What should reviewers focus on?

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

[ebwu95]

once the intake form is submitted we should show them like this screen