Create new Orchestrator definition.

[Carsopre]

Kind of request

Adding new functionality

Enhancement Description

• Rename runners into orchestrators.
• Create new OrchestratorProtocol that inherits from AnalysisProtocol (which should only have the execute() method.
• Rename DamageAnalysisRunner and LossesAnalysisRunner to xxxxAnalysis.
• Remove AdaptationAnalysisRunner.
• Adaptation class should now be moved to the subproject orchestratros and implement the OrchestratorProtocol.
• Ra2ceHandler will call orchestrators and not "runners". The runner factory can have now some extended logic that will determine which of the available orchestratos will be used.
  • When damages and losses are present, only the former is taken (so DamagesAnalysis).
  • When only damages or losses are present, the corresponding orchestrator is used.
  • When adaptation is present only Adaptation is used.
• Replace / update the related class diagrams and other documentation.

Use case

We need an "orchestrator" type that takes over the current role of the runners. We consider orchestrators as a type of analyses that can call and modify the existing base analyses (for now Damages and Losses).
This also implies the creation of the new orchestrators subproject.

Additional Context

Although this looks like just a "rebranding" of the runners subproject, the implementation of different protocols is going to allow us to provide the user with more freedom on how to call each of the orchestrators, which in practice will represent the formalization of different workflows seen in real cases (like adaptation or uncertainty).