Separate pure dynamic Models from dynamic with static reference Models

[flo-dup]

Do you want to request a feature or report a bug? Feature

What is the current behavior? Pure dynamic Models and dynamic with static reference Models inherits from the same BlackBoxModel, but

• pure dynamic models have en empty string as staticId, reflecting the optional staticId in dynawo blackBoxModels
• pure dynamic models return an empty list of varsMapping, reflecting the optional corresponding MacroStaticRef

What is the expected behavior? Having two separate Classes:

• one for pure dynamic Models
• one for dynamic with static reference Models

What is the motivation / use case for changing the behavior? Clear separation of what is purely dynamic from what is linked to static equipment

[flo-dup]

After working on the topic in #136, we decided not to separate in two classes non-static and static refererenced models. We kept the logic which is behind dynawo by only separating BlackBoxModels from the default models, also called Network models, which are created if no mapping is defined on some equipments. Closing this issue as a consequence.