Feat/clerk web + shared + mobile

[manueltorres0]

Description

• added clerk provider wrappers to mobile and web clients to allow them to use clerk auth hooks
• protected web routes
• Added sign-in/up flows, and basic components for web
• added redirect configuration for Oauth use on mobile
• updated API client to attatch Clerk session tokens to requests in the shared folder
• had to generalize the api client in the shared folder more because each client's useAuth hook comes from a different framework, so made a custom client for web and mobile (useAPIClient)

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (code improvement without changing functionality)
• Documentation update
• Configuration/infrastructure change
• Performance improvement
• Test coverage improvement

Related Issue(s)

Related to #71

What Changed?

• Clerk integrated to the frontend clients, the frontend clients now have access to clerk auth utilities, and for the case of web: pages are protected by signed in checks
• Added the sign in/out components in web
• Added the api client helper to both web and mobile to wrap requests with auth headers

Testing & Validation

How this was tested

1. Used test api endpoint
2. Signed in / signed up / and logged out on web

Unfinished Work & Known Issues

• None, this PR is complete and production-ready
• The following items are intentionally deferred:
  • *** The sign in, log in, sign out cards for mobile
    I think you guys intentionally did not ask for these components in the ticket, so I did not implement it.

Notes & Nuances

NONE

Pre-Merge Checklist

Code Quality

• Code follows the project's style guidelines and conventions
• Self-review completed (I've reviewed my own code for obvious issues)
• No debugging code, console logs, or commented-out code left behind
• No merge conflicts with the base branch
• Meaningful commit messages that explain the "why"

Testing & CI

• All CI checks are passing
• All new and existing tests pass locally
• Test coverage hasn't decreased (or decrease is justified)
• Linting passes without errors

Documentation

• Code is self-documenting or includes helpful comments for complex logic
• API documentation updated (if backend endpoints changed)
• Type definitions are accurate and up-to-date

Reviewer Notes

If I misunderstood and you guys meant to include the sign in /log in /sign out components for mobile in this ticket,
please let me know.

• Areas needing extra attention: ...
• Questions for reviewers: ...