New simulation time series plugin

[jorgenherje]

Create new simulation time series plugin SimulationTimeSeries

Based on the functionality in original ReservoirSimulationTimeSeries plugin, with additional functionality requests listed in following issue: #698.

This PR includes and closes parts of the listed requests:

• Show multiple delta ensembles - create delta ensembles
• Stacking possibility - subplot per vector and subplot per ensemble

---

Review feedback

Please give feedback on following points:

• Naming of objects in _property_serialization-folder
• Naming of objects in types-folder
• Can utility functions in utils-folder be handy for others and placed in webviz-subsurface/_utils-folder?
• Consider moving ProviderSet to webviz_subsurface/_utils-folder. Could be reusable, and additional functionality can be added based on needs.

---

Summary

The work includes structuring and refactoring of code for enhanced plugin implementation. Goal is to have code separated on functionality (callbacks, layout, business logic etc.), convert dash property to strongly typed arguments for "business logic". Clarifies intended usage and testability, preventing loosely typed arguments resulting in passing incorrect data.

Utilize best practice example in webviz-plugin-boilerplate.

---

Main points

• Use ensemble summary data providers - Ensemble summary provider #721
  • Allows resampling frequency selectable
• Refactor and structure code for readability
  • Separate code dependent - layout, callback and business logic used in callback
  • Improve testability unit tests
  • Use boilerplate best practice plugin - webviz-plugin-boilerplate
  • Introduce strongly typed functionality for enhanced readability and more strict interfaces
• Show multiple Delta Ensemble:
  • Create Delta Ensemble
  • Delta Ensemble as selectable ensemble
• Group by:
  • vectors - subplots per selected vector
  • ensemble - subplots per selected ensemble

---

Todo

• Unit testing of "business logic"

[anders-kiaer]

Great work @jorgenherje 👏🚀 Looks nice!

I like that you also apparently has laid the ground for reusing parts of the functions in other plugins as well going forward.

There are some TODOs in the code (I've only commented on a couple of them). Should we stick with them in code only, or should we make issue of them as well as reminders?

Besides that I have only a couple of minor comments, then this is ready to merge IMO when we see green light towards example data.