Move Forbidden Error Handling from Chat MS to Gateway

In the current implementation, some 403 Forbidden errors are thrown at the microservice level. Where possible, this error handling should be moved to the API Gateway by implementing appropriate middlewares and guards.
Centralizing access control at the gateway level improves consistency, simplifies microservice logic, and enhances maintainability across the system.