174 backend frontend implement clerk user id to retrive user data

[mva919]

What type of PR is this? (Check all that apply)

• [x] ✨feature: Introduces completely new code or new features.
• [ ] 🐛fix: Implements changes that fix a bug. Ideally, reference an issue if present.
• [ ] ♻️refactor: Includes any code-related change that is neither a fix nor a feature.
• [ ] ✅build: Encompasses all changes related to the build of the software, including changes to dependencies or the addition of new ones.
• [ ] ⚡️test: Pertains to all changes regarding tests, whether adding new tests or modifying existing ones.
• [ ] 🚰ci: Involves all changes related to the configuration of continuous integration, such as GitHub Actions or other CI systems.
• [ ] 📚docs: Includes all changes to documentation, such as README files, or any other documentation present in the repository.
• [ ] 🗑️chore: Captures all changes to the repository that do not fit into the above categories.

Description

What did you change? How did you change it?

• Make user creation api
• Add ClerkId field to prisma schema (idk why the whole file got reformatted but that's the only thing I changed : P)
• Edit app layout to render sign in auth screen if the user is not logged in, else rendering our app
• Use new user creation api in global context to create the logged in user if the user is new, else retrieving existing user data then setting that data in the global context
• Add unit tests for sign out and sign in with google components
• Create username generator for instances where the username field is null when retrieved from clerk
• Fix the enabling of the sign in button with an useState hook

Tests

How was this tested?

• [x] Unit tests
• [ ] Integration tests
• [ ] E2E tests
• [ ] Manual tests
• [ ] Tests were NOT needed
• [ ] Other (explain below)

[Optional] Screenshots

Documentation

• [ ] Added to README.me
• [ ] Seperate document
• [x] NO documentation needed

Link to external documentation:

[Optional] Are there any post-deployment tasks we need to perform?

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.35%. Comparing base (32e9300) to head (bb75aaf).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #180 +/- ## ========================================== + Coverage 69.23% 74.35% +5.12% ========================================== Files 17 20 +3 Lines 130 156 +26 Branches 36 40 +4 ========================================== + Hits 90 116 +26 Misses 40 40 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[thienguen]

reviewing now

[thienguen]

Believe you also fixed issue of user come back after the prev session cleared, erm, they should just login since its SSO.

Approved.