Feat/integrate profile posts

[robertocarlous]

Closes #276

Summary

This PR updates the profile page to use the dedicated user-specific posts endpoint instead of relying on the generic posts endpoint with query parameters.

Problem

The profile page previously fetched data from:

/api/posts?userId=...

This approach relied on a contract that is not guaranteed by the generic posts endpoint, leading to inconsistent data handling and tight coupling to an unreliable response shape.

What Was Done

Switched profile page data fetching to:

GET /api/users/[id]/posts
Removed dependency on /api/posts?userId=...
Normalized API response to align with PostCard component requirements
Updated data mapping logic to ensure consistent rendering
Result
Profile page now consumes a stable, dedicated API contract
Improved reliability and maintainability of post data fetching
Reduced assumptions about backend response structure
Verification
Profile page successfully fetches posts from GET /api/users/[id]/posts
Posts render correctly using PostCard
Follow/unfollow functionality remains intact
Tab filters (posts, replies, media, etc.) work as expected with server data

[drips-wave]

@robertocarlous Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[3m1n3nc3]

Closes #276

Please update your PR message and add a proper description of all the changes you made.

[robertocarlous]

Pls check