Fix issue when updating database for clusters that were previously deleted before upgrade to 2.2 database.

    IDLE (in case the previous node state was DOWN).

    job is in a pending state, then send the request directly to the slurmctld
    daemon and do not attempt to send the request to slurmd daemons, which are
    not running the job anyway.

    consider the job's time limit when attempting to backfill schedule. The job
    will just be preempted as needed at any time.

    Priority.

    expected start time was too far in the future for the backfill scheduler
    to compute.

    values as "*" rather than 65534. Patch from Rod Schulz, BULL.

    the job's priority using scontrol's "update jobid=..." rather than its 
    "hold" or "holdu" commands.

Fixed issue when using a storage_accounting plugin directly without the slurmDBD updates weren't always sent correctly to the slurmctld, appears to OS dependent, reported by Fredrik Tegenfeldt.

    it were removed from the job's allocation. Now only the tasks on those
    nodes are terminated.

Fix for checking QOS to override partition limits, previously if not using QOS some limits would be overlooked.

CPUS = SOCKETS * CORES
but THREADS != 1
in that case, reset select/cons_res internal node table to thread count = 1

    SelectTypeParameters=CR_ONE_TASK_PER_CORE.