Chore/clerk user id migration

[manueltorres0]

Description

• changed the user model, table and endpoints to use the id given by clerk as the primary id, dropping our db generated id

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)

Closes #88

What Changed?

• the models for users now only contain a single id (provided by clerk)
• the user table only contains one id
• the endpoints accept and return a single id

Testing & Validation

How this was tested

1. made sure all previous tests passed

Unfinished Work & Known Issues

• None, this PR is complete and production-ready
• The following items are intentionally deferred:

  • ---

  • ---

  • ---

Notes & Nuances

• ---

• ---

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

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