[Greencity API] Incorrect 404 Not Found Response in Swagger Documentation for Greencity API Endpoints

[marim87]

Environment: Windows 10 Pro, Google Chrome Version 130.0.6723.117 (Official Build) (64-bit).
Reproducible: always
Build found: commit [487e4c0] (ita-social-projects/GreenCityClient@487e4c0)

The Swagger documentation for the Greencity API currently specifies that a 404 Not Found response code can be returned for the following requests:

GET /friends/not-friends-yet
GET /friends/friendRequests
However, these endpoints do not include any path parameters, and as such, the 404 Not Found response code should not be supported in the Swagger documentation for these specific requests.

Additionally, when executing requests for non-existent resources (exasmple: GET /friends/not-friends-yetyet or GET /friends/friendRequestsSS), the API returns a 403 Forbidden response code instead of the expected 404 Not Found response code for non-existent resources. This discrepancy between expected and actual behavior should be addressed.
Please find attached examples of requests from Postman.

Acceptance Criteria
Remove the 404 Not Found response code from the Swagger documentation for GET /friends/not-friends-yet and GET /friends/friendRequests endpoints.
Update the Swagger documentation to reflect the correct expected response codes for these endpoints.
Investigate and correct the API behavior to return 404 Not Found for non-existent resources, instead of 403 Forbidden.