Dynamic container jobs #311
Description
Currently jobs are fully resolved at script initialization, which means MonkeyCI expects a sequence of jobs, either container or action jobs. We could make this more flexible by not resolving functions at initialization time, but the problem is we don't known which other jobs it's dependent on.
An alternative is to allow action jobs to create container jobs. We would have to see how this could be implemented though.
Or we could allow container jobs to have an "initializer" function, which is invoked at job startup time, and should return the job configuration (instead of providing it at config time).