CapacityScheduler should have prevent a single job taking over large parts of a cluster

The proposal is to have a per-queue limit on the number of concurrent tasks a job can run on a cluster.

We've seen cases where a single, large, job took over a majority of the cluster - worse, it meant that any bug in it caused issues for both the NameNode and the JobTracker.