creating master-queue name and updating the 
way the queues are setup
cleaning up how blue-collar maintain key and queue
names by putting it into its own ns

moving toward a master job site, currently
core starts it, but no work goes to it
adding ability to specify a named processing queue
removing server name from JobPlan
getting the master job site up and running, 
and as a result caused some domino effect 
failures that need cleanup still
completed the task of making the master queue
where all jobs are first pushed and then
are delegated to their appropriate queue
once processed server side
handling the case if something was stuck in the 
master processing queue and cleaning it up
on startup
Merge remote-tracking branch 'origin' into master-queue