Job Streams corrections and improvement

This issue summarizes several corrections and improvements in the first Job Stream release

• when an In Condition expression contains an event definition such as mystream:Event, this expression is not connected correctly to an Out Condition that creates the event myEvent.
• The remote reference sometimes is not displayed correctly.
• Jobs should be started with "force=no"
• It should be possible to define the job start with "force=yes"
  • Example 1: at=now, force=yes
  • Example 2: now,force=yes
• The commands parameter for the job start can be empty. Then the job will be started with at=now, force=no
• The start_job command should consider assigned calendars+restrictions (e.g. every_day calendar  + only monday restriction)