feat: add profile patch endpoints and integrate with auth middleware

[mehmetcangurbuz08]

This PR adds patch endpoints to the profiles module and protects related routes with auth middleware.

Changes:

Added GET /me and profile patch flows
Added patch endpoints for me, physical, health, location, and privacy
Enforced JWT-based user access on profiles routes
Standardized validation and error responses
Fixed privacy enum type issue in repository query
Testing:

Manually tested endpoints with a valid auth token
Verified GET /me response after patch operations

Closes #106

[AlperKartkaya]

It is a well-implemented good feature. There is just one critical blocker to address: PATCH /api/profiles/me is currently broken for partial updates after a profile already exists.

When tested this flow:

1. create profile with firstName + lastName -> works
2. patch only phoneNumber -> returns 500

Root cause seems to be in backend/src/modules/profiles/repository.js: upsertProfileByUserId() still tries to insert null first_name / last_name, but those DB columns are NOT NULL, so Postgres rejects the request before the conflict update helps.

This is merge-blocking because a normal profile update flow is broken.

Can you please consider fixing this by using update logic for existing profiles and keeping the create/upsert path only for first profile creation?

[AlperKartkaya]

The issue is fixed now, merging the PR.