Intersection module and backend

[HansKallekleiv]

The PR #267 is an investigation into solving these user stories:

• User stories for 4D analysis #353
• User stories for investigating structural uncertainty #354

Investigations/conclusions/follow ups below (in progress):

1. Create a SeismicAccess class towards Sumo and assess the if the current metadata is adequate for our use
   Conclusion: (Most) metadata is available and retrieval of cube works fine. Ready for implementation. Add Sumo SeismicAccess #350

• Evaluate using well trajectories from SMDA as intersection source
  Conclusion: Works fine. Request for relevant well data already implemented in TopographicMap module with mesh/property surfaces, fault polygons and official well trajectories #263

• Create a VdsAccess class towards a hosted service of vds-slice for extracting seismic slices on-the-fly
  Conclusion: Performance is good on tested cubes. Ready for implementation: Add VDS Access #319

• Evaluate performance of slicing grid geometry using xtgeo
  Conclusion: Requires user-session due to data size and computation time. Xtgeo handles the intersection logic so not much code to add. Performance is ok for smaller simulation grids, but will be an issue for larger grids. We should investigate if the compution can be improved, but it will have value to implement in its current state. Add backend functionality for intersection data #352

• Evaluate performance of slicing multiple surfaces using xtgeo
  Conclusion: Requires user-session / redis? to keep the surfaces when switching between wells. The intersection logic is handled by xtgeo and is fairly fast. Can be implemented. Add backend functionality for intersection data #352

• Investigate using esv-intersection module as visualization component for intersections
  Conclusion: The visualization is a good candidate for visualizing intersections and could be implemented. Add visualization component for intersections #351

• Visualize multiple intersections side-by-side in a dashboard together with a map module using synced settings
  Conclusion: Synced setting works for e.g. syncing selected well, but could become an issue when many settings should be synced between views. Needs further investigation on how to sync e.g. time interval/ colors/ zoom and bounds