feat: Integrate Matches page with backend

### Problem / Motivation

Implement matches page that’s hooked up to the backend
Remove phone number on matches page (we dont collect this info)
Fill in the matches card with dynamic info

### Proposal

Update the Matches page to display real mutual matches from the backend instead of the current placeholder/hardcoded information.
The frontend should fetch the user’s mutual matches from the matches endpoint and dynamically populate the existing match cards with the information returned for each matched user.
# As part of this implementation:
Connect the Matches page to the mutual matches backend endpoint.
Replace all mock/placeholder match information with real user data.
Populate each match card dynamically using the matched user’s profile information.
Remove the phone number field from the match card since MeteorMate does not collect users’ phone numbers.
Handle loading, empty, and error states when retrieving matches.
If the user has no matches yet, display an appropriate empty state message rather than showing placeholder cards.

UI:
The existing Matches page design should be reused, with the cards populated using real backend data.
The phone number section should be removed from the current UI, while the remaining available profile/contact information should be displayed dynamically.

Flow:
Matches Page → Fetch mutual matches → Populate match cards with real user data
If no mutual matches are returned, display a clear “No matches yet” state instead of an empty or incomplete page.

### Acceptance criteria

_No response_