Job Streams should have a job stream starter that creates a context for events

Current Situation

• Job Streams use the context "day period" where period is from 00:00 to 24:00 (UTC). Each event that is created in this context can be consumed by In Condition expressions.
• Job Streams will be started by starting a job that creates events.
• There are no parameters for job streams.
• There is no job stream history.

Desired Behavior

• There should be a job stream starter.
• The job stream starter has a run time.
• The job stream starter defines parameters.
• There is a list of jobs that is assigned to the job stream starter.
• Each assigned job may have a delay to start the job with this delay by the job stream starter.
• The job stream starter can be started manually or by run time.
• Each start defines a new context.
• The assigned jobs will be started. Each event that is created with this context can be consumed by the expression in In Conditions.
• When a job is started with this context by an In Condition expression then the events created by the Out Conditions will have the same context.
• Global events will use a period as the context. The period begin is configurable.
• When consuming events from another job stream the context is also the period.