CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

The queues are stored in a ConcurrentHashMap and the code already checks for a null queue. At best we need to lock individual queues when processing the access check, but I don't see why we need to grab the highly-contested scheduler lock to lookup which queue to use for the hasAccess call.