Queueing/Multi-Jobs/Release in Build Pipeline

* Scheduling (Queueing) of Jobs in the pipeline:
  - by defining time-intervals on jobs, certain daily times for deployment can be enforced (e.g. prod only at night)
  - queued jobs are marked in the pipeline and blocked (except for cancel) 
* Correct LastSuccessful Build Information for Jobs used by multiple Build Pipelines
  When a job is parametrized and used in multiple Build Pipelines, the last successful information in the project headers was not correct. After the grid is built, the code now runs through it and corrects this information.  
* M2Releases can now be run directly from the pipeline
  By adding the dependency to the maven-release-plugin, it is possible to run "perform maven release" from the pipeline view (new icon on top, aside the "run" icon), seems very convenient.
* Draw lines (mosaic style) between pipeline builds resp. headers
  For complex pipelines, the green "next" arrows were not clear enough showing the dependencies. We decided to implement a tile-based visualization for the dependencies. It also works if jobs downstream are used multiple times on one pipeline.
* Added Icon for Manual Triggers
  Whether a job is manual triggered is given by the definition of the jobs, in order to visualize that fact, we put an icon into the build-form.
* Queued Jobs now visible in multiple pipelines
  When queueing jobs which are used in multiple pipelines or multiple job-instances in the same pipeline, upstream and downstream dependencies need some more logic.
* Display of params in Headers was wrong for same parameters in multiple jobs, now last wins, as for the job execution
* Retry now works with queuing and replacing builds in the pipeline (did not before)