scheduler: canary system jobs fail to deploy correctly in clusters with infeasible nodes

When deploying canaries in clusters that have infeasible nodes, canary count is off and it can lead to deployment constantly hanging. This is due to the fact that canary node count is calculated based on the number of _eligible_ nodes and doesn't correctly subtract nodes that aren't feasible from that. 