initializaton of AGILE components

[cskiraly]

Some AGILE components need to start/stop based external conditions e.g. available HW, etc.
docker-compose in itself is not meant to handle this. This issue is to keep track of the discussions on what solution we choose to handle component initialization.

Related: Agile-IoT/agile-stack#15

[nopbyte]

We have also previously discussed wit h @cskiraly an initial approach to have a multi-user node-red environment. The idea would be to execute separate node-red instances, i.e. separate containers, for each user.
In this case, we would need to start and tear down different containers during runtime. It sounds to me that, even though both use cases are not the same, they may both benefit from a mechanism to start and stop new containers based on some information that is not available when the agile stack starts.