Resolve mapstruct warnings from logs

### Objective
Currently the mappers present some warnings that are displayed in logs when you make `./mvnw clean compile` is possible view because the **mapstruct verbosity** is active, some warnings can be problematic since are related to other sub **mapstructs** that are **unmapped**. Therefor to improve the process of generating the implementation class for every mapper this type of warnings needs to be fixed


### Checklist

- [ ] Review every warning in the logs related to **mapstruct**
- [ ] If it's possible fix the unmapped warnings related to mappers

Start by running `./mvnw clean compile` and reviewing the MapStruct warnings shown in the build logs. Trace each warning to its mapper and determine whether the unmapped fields should be handled; done means the relevant MapStruct warnings are resolved or documented as intentional.

Written by the indexing model from the issue text.