K1 20 anonymize user data update clerk auth setup

[theop04]

Developer: Theodore Weicker

Closes #K1-20

Pull Request Summary

To create separate player and admin login pipelines (so that kids' emails are not collected)

Modifications

Files created:

• adminDashboard (not in the ticket, but was necessary)
• player sign up page (not in the ticket, but was necessary)
• page to direct to player/admin login pages
• both player and admin login pages
• modification: removed admin sign up page (invite only) and made it necessary to add admin privileges to metadata on Clerk. Simply paste this to public metadata: { "role": "admin" }

Testing Considerations

• tested standard admin route and player route for respective accounts
• tested player account signing into admin dashboard
• tested admin account signing into player dashboard
• tested new player sign up functionality

Pull Request Checklist

• Code is neat, readable, and works
• Comments are appropriate
• The commit messages follows our guidelines
• The developer name is specified
• The summary is completed
• Assign reviewers

Screenshots/Screencast

{put screenshots of your change, or even better a screencast displaying the functionality}

Note: the "email" description cannot be removed from the login page

[kaseyliu]

Hi Theodore, thanks for doing this, and thanks for clarifying the vague parts! A few things:

• It doesn't seem to matter what password I put in for admin when I log in. As long as I do the 2FA on my email and enter the code, I can log in. Can you add password verification too, in addition to having to put in the 2FA code?

• Also, could you add a button to bring the player to the signup page in the login page? I think you can do this in Clerk, like add a "Create Account" button under some text like "Don't have an account?"