(Matching Service) Implement JWT Validation

[hyc17003]

Description

The matching service currently lacks JWT validation on its endpoints. This allows any client to call the matching APIs without authentication, posing security risks such as unauthorized access, impersonation, and queue manipulation.

Current Behavior

1. Matching endpoints accept requests without authentication
2. userId is passed in request body or query parameters but not validated
3. No verification that the requesting user is who they claim to be

Expected Behavior

• All matching service endpoints require a valid JWT
• JWT is validated and user identity is verified
• userId is extracted from the verified JWT, not from request parameters
• Unauthorized or invalid requests return appropriate 401 or 403 errors