Implement Well Log Viewer Module

[Anders2303]

Resolves issue #683

Adds a wrapper module for the Subsurface WellLogViewer.

TODOs

This uses the readout box and sortable list components introduced in other PRs, those should be reviewed and merged first

• Await merge of Implementation of SortableList component (+ sub components) and menu utility components #685
• Await merge of Replace Intersection and 3D viewer readout boxes with shared comp #707
• Await merge of Module unload and persistent module atoms #717

Specifications (1st iteration):

• Settings
  • Dropdown for selecting ensemble
  • Load available wellbores for field given by selected ensemble from backend
  • Dropdown for selecting wellbore
  • Definition of logs (columns) - Intersection module with its layer manager could give some inspiration
• View
  • Use well-log-viewer component to visualize well log defined in settings
  • Load data required for visualization from backend
• Define interface for sending log definitions, ensemble, and wellbore from settings to view

Specifications (2nd iteration):

• Setting sync
  • Ensemble
    • Skipped this one, we dont have any existing setup for synced field
  • Wellbore
• View
  • Show curve info on hover
    • Subsurface component is currently not emitting data properly, see Well Log Viewer: Expose computed track info values webviz-subsurface-components#2196 . Will fix that first, before implementing this
  • Sync hovered MD with and subscribe to MD hover from other modules
• Colors
  • Avoid random colors each re-render
  • Make colors update when workbench color settings are changed
  • User color selection

Specifications (3rd iteration):

• Extra curve types
  • Diff curves.
  • Discrete curves. The viewer supports it, but requires a "discrete_metadata" field for the well-log. How do we fetch or set up these?
• Settings
  • Map out other settings in the subsurface component, and see what makes sense to expose for our users
    • Horizontal/vertical orientation
    • Curve-specific scales
  • Make definitions of log storable in and selectable from local storage (maybe in addition or alternatively savable as/loadable from JSON file)

Specifications (4th iteration):

• Evaluate if component created by Aspentech is sufficient - maybe it requires refactoring to fit into our application (e.g. remove legend and primary scale and make it possible to define these on the outside via props/callbacks)