Document 401 Unauthorized HTTP status error on Swagger UI for every API

## Description

As a frontend developer,
I need to know the available responses from the API,
so that I can properly adjust frontend for the potential responses.

Documentation about the 401 Unauthorize HTTP status is missing from Swagger UI. The idea is for this to be documented, and Swagger UI acknowledge that the 401 documentation exists. This happens at least for `PATCH /sections/{id}`, but I am pretty sure it is happening with all endpoints.

## Mocks

You can see in the following message, the 401 shows as undocumented.


## Acceptance Criteria
### Update [Required]
- [ ] Every API should have 401 Unauthrized HTTP status documented on Swagger UI

## Definition of Done
- [ ] All of the required items are completed.
- [ ] Approval by 1 mentor.

## Estimation

2 hours