Revoking Admin privilage in Visit History and creating valid pydantic schemas for Visit history and Consultation History using Camp Visit Id

🔌 API Issue

Describe the API issue

The GET /api/v1/users/{user_id}/visit-history endpoint requires an update to its role-based access control logic to properly enforce admin privileges.

Additionally, response schemas are currently missing or not properly defined for the following endpoints:

• GET /api/v1/users/{user_id}/visit-history
• GET /api/v1/consultations/camp-visit/{camp_visit_id}/consultation-history

This results in:

• Inconsistent or loosely structured API responses
• Lack of proper Swagger/OpenAPI documentation
• Potential security concerns due to improper access validation

---

API Endpoint (if applicable)

1. GET /api/v1/users/{user_id}/visit-history
2. GET /api/v1/consultations/camp-visit/{camp_visit_id}/consultation-history

---