Allow any config to go through docker without having to explicitly define them the entrypoint.sh file

[rishabhpoddar]

🚀 Feature

This is in accordance to #74.

In the way we are architecting recipes, there can be a random set of configuration values that may be needed by the recipe. This requires that env variables passed to a docker container can handle any such variables and put them in the config.yaml file.

If this is not possible, we will have to change the core to read config values from:

• The OS env; and then
• The config.yaml file

Since docker env are flat, we must also make sure that the config values do not clash across recipes. This can be done by each config value for a recipe is prefixed with the rId. For example, a recipe called emailpassword will have all its config values like email_password_*.