Consider a context provider wrapping view and settings components in order to more easily access framework helpers

[rubenthoms]

Implement a module-instance-specific context and provide it to settings and view components. This context could provide workbench and module instance information (session, services, settings). Specific hooks could then use this context in order to provide functionality like adding messages to the status writer or get ensembles etc.

Advantages

• Reduce prop-drilling
• Make framework-interaction easier accessible
• Easier task-related code separation
• Very React-ish

Disadvantages

• Might be harder to see what goes where / who is consuming what