Conflicts:
	src/plugins/sched/backfill/backfill.c
	src/slurmctld/job_mgr.c

Remove some debugging logic accidentally included in commit
7a187f10

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

Log more backfill scheduling actions including where/when jobs will run even if they can not start until long in the future

file.

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

Conflicts:
	src/common/gres.c

When they fail, only the first line of the test description in README
is output, so we want it to capture the nature of the failure on
that first line.

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

in QoS and that the first limit on the GrpNode limit is used in
an association.

Add array ID to job signal logs

Avoid duplicate "job Jobid=#"
Avoid printing "arrayid" and "taskid" by printing using standard
   Slurm formats
Add job array and state information to job recovery log

Add job "reboot" option for Linux clusters. This invokes the configured
RebootProgram to reboot nodes allocated to a job before it begins execution.

Put things in alphabetic order.
Fix extern definition to be more clear.

This does not fully implement the option, only permits its use from
commands to submit jobs and updates the documentation accordingly.