Adding support for multiple configured job names

Before this change the User could either have one named job or all jobs run by default.  Beyond being limiting, because of the sequencing it forced the User to "re-register" their Jobs into the JobRegistry, even if they were <code>@Beans</code>.  The processing would have found them as beans in subsequent processing but exceptions triggered by their absence in the JobRegistry prevented that.  

This change allows for multiple named jobs to be executed by changing the configuration to allow a comma-delimited list of jobs.  It also changes the processing flow to first find the Jobs as Beans, then in the JobRegistry (which the User can customize).  Minor Javadoc changes and fixes that relate to this as well.