Refactor existing analyses

[Carsopre]

Kind of request

Changing existing functionality

Enhancement Description

Update all different Damages and Losses analyses so that they implement the corresponding interfaces and base classes as seen in the proposed diagram of #602.

In addition, categorize those analyses such as OriginClosestDestination which could be consider as PartialAnalyses, these sort of analyses cannot stand on their own and depend on the call from an implementation of the AnalysisBase. In addition their output does not need to be an AnalysisResultWrapper.

Use case

Make a distinction between BaseAnalysei and OrchestratorAnalysis.
An OrchestratorAnalysis will use one or many different BaseAnalysis throughout its lifecycle, combining for instance Damages and Losses. A BaseAnalysis can only use its own definitions or parent classes.

Additional Context