Study configurable default configuration for insights

Current situation

We can provide insights definitions via an environment variable. This is great. But we would like to be able to create a docker image that provide its own set of insights definitions (including css items).

A simple use case we would like to cover is:

We have the allinone image which uses the built-in insights.

We want to create a yada-orchestrator image that is based on the allinone image (that is, its Dockerfile has a FROM opentestfactory/allinone statement) and provide its own insights definitions.

Desired outcome

This study should propose a mechanism to enable such a use case. In other words, how we can do that today if we can already do that today, and what change should be made if we cannot do that today.