<DO NOT MERGE> Coding dojo: refactor to apply aggregate root pattern in DiseaseOutbreakEvent + IncidentManagementTeam

[anagperal]

📌 References

• Issue: Closes Q4 2024 Project Coding Dojo

📝 Implementation

• Delete IncidentManagementTeamD2Repository and add functions directly to DiseaseOutbreakEventD2Repository
• Delete from CompositionRoot functions related to incidentManagementTeam and move it to diseaseOutbreakEvent
• Delete getIncidentManagementTeamMember (in repo and usecase) and get in GetDiseaseOutbreakByIdUseCase the incident manager using the incidentManagerName filtering incidentManagementTeam
• Review deleteIncidentManagementTeamMemberRole and saveIncidentManagementTeamMemberRole and have in params only necessary, do not condition the domain to what the repo endpoint needs (remove roles from params and improve code)
• create GetDiseaseOutbreakEventAggregateRootByIdUseCase, DiseaseOutbreakEventAggregateRoot and IncidentManagementTeamInAggregateRoot in order to apply aggregate root pattern in Incident Management Team Builder page
• Create the Incident Management Team in hook useIncidentManagementTeamView from IncidentManagementTeamInAggregateRoot + TeamMember[] + Role[] = new entity in presentation layer
• Add roles and team members in AppContext
• Delete all related to IncidentManagementTeam as entity and leave it as IncidentManagementTeamInAggregateRoot. IncidentManagementTeam will be the entity used in Presentation Layer
• Add comments in functions and classes with aggregate root working in parallel with old code (add @ deprecated)

Future:

• Create/update/delete of children done through DiseaseOutbreakEventAggregateRoot entity
• In DiseaseOutbreakEventRepository when save IncidentManagementTeamMemberRole send DiseaseOutbreakEventAggregateRoot and check what is new to save it

📹 Screenshots/Screen capture

🔥 Notes to the tester

[xurxodev]

thanks @anagperal

I approve this PR because it is the beginning of a very big refactor and some things are temporal.

However, I leave here all things I saw:

• In the future, DiseaseOutbreakEventTestRepository only should have: get, getById, save and delete. We should save and return always the aggregate root, and we should not have methods to retrieve only children.
• Great to request roles and team members to start the app using app context but we should not have GetConfigurationsUseCase and GetConfigurationsRepository. roles, teamMembers and incidentManagers are different entities y should have different use cases and repositories, all called to start the app. Configurations entity doesn’t exist.
• I understand that the keyword AgreggateRoot is to identify old code and new code, in the future I would remove this keyword of entities, functions, etc..
• Great to add validations to new aggregate root to addTeamMemberToIncidentManagementTeamHierarchy, in the future we would need add tests for this validations using the aggregate root
• In the future all validations related to aggregate root should be done in the entity