Expand from 8 to 16 bits for more than 256 sizes

sched/backfill - Fix anomaly that could result in jobs being scheduled out
of order.
bug 911

Without this a batch script could be bound to a single CPU rather
than the full job allocation. This is a revision to commit
399cb897
without which batch scripts has no binding to CPUs via hwloc

squeue and scontrol to report a job's "shared" value based upon partition
options rather than reporting "unknown" if job submission does not use
--exclusive or --shared option.
bug 939

exit code.

a fix to handle sacct under this new method.

signal to the batch script only.

process terminated by a signal.

error message and avoid to loop forever, give up after 120 seconds.

This reverts commit 53706b41.

Conflicts:

	NEWS

Report correct partition associated with a step if the job is submitted to
multiple partitions. Previously all of the partitions that the job could
run in would be reported for the step.

Without this, the record of gres allocated to steps will remain
allocated and not be available to job steps after being requeued.

sched/backfill - If job started with infinite time limit, set its end_time
one year in the future. Previous logic would based it upon INFINITE and
produce an overflow of the uint32_t time.

Report correct CPU count allocated to job when allocated whole node even if
not using all CPUs.
bug 909

Fix bug which could report to squeue the wrong partition for a running job
that is submitted to multiple partitions.

you could get multiple '*' wckeys.

deleting users.

able to be destroyed for debug.

sched/backfill: Correct job start time estimate with advanced reservations.
Under some conditions, the job start time would be set to the end time
of an advanced reservation that may have nothing to do with that job's
resource requirements.
bug 911

file.

If we don't it could get messed up on a reconfig.

Logic used to identify cores which are usable with each GRES weas incorrect.
bug 905

QOS had a GrpNodes set.

Fix for core-based advanced reservations where the distribution of cores
across nodes is not even. Failing test case:
system has 10 nodes, 1 of which is fully occupied
create reservation with 9 nodes and 10 cores
always would fail with "busy nodes" error