I-rh01 to I-rh07 - Fixes and enhancements as described below

* I-rh01 - Scheduling of Jobs in the pipeline:
  In our environment, for each stage we have distinct time-intervals per day when deployment is possible. In order to respect that, still have immediate feedback in Jenkins when the job is running, but without blocking any Jenkins Threads we implemented such a feature. Several changes in multiple files had to be made for that to be running. The way it works:
  - on a certain job, an interval (start-time, end-time) is specified
  - when a trigger (manual or automatic) is hit, the interval of the job is respected and the job is queued accordingly
  - the build-pipeline shows this (new) state and displays the time of start and the waiting time till then
  - if no interval is defined, all goes normal as of today
  - if the time of trigger is after the last interval, the queuing is wrapped around to the next day
  
* I-rh02 - Avoid display of sensitive Parameters in Headers/Revisions 
  As of today, if a parameter for a pipeline build contained a password, that was displayed in clear text on the screen. By filtering the parameters for sensitive values, this is now avoided.
 
* I-rh03 - 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.
  
* I-rh04 - Starts with parameter fails if the first job has no parameters
  Corrected this behaviour by also checking the actual job, if it has parameters at all.
  
* I-rh05 - M2Releases should 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.
  
* I-rh06 - Draw lines 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.

* I-rh07 - Added Icon for Manual Triggers (always)
  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. The icon could be nicer :-)