<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)

📹 Screenshots/Screen capture

🔥 Notes to the tester