Include explicit values so some can be removed in successive commits.

Missed in BlueGene code removal.

# Conflicts:
#	src/slurmctld/read_config.c

Bug 6302
Bug 6229

this new function adds logic to validate that a job's gres request is
still valid after slurmctld restart or reconfiguration. specifically
if a job allocation includes GRES associated with specific Files then
kill the job if the GRES count changes (say the job is allocated GPUs
and the slurmctld configuration changes to remove those GPUs, so the
job and node bitmaps are different sizes).

This prevents a slurmctld abort if a job was running on a node
  using all gres/gpu and the node configuration changed to have
  fewer gres/gpu. slurmctld would abort on restart with the new
  configuration.

Previous logic was calculating a node's total cores and total threads
in multiple locations rather than doing the calculation only in the
function gres_plugin_node_config_validate().

string.

Bug 6169

bug 6169

This reverts commit 34633d9b.

Bug 6169

Added extra check of name in setenvf() to ensure name is not an empty
string.

bug 6169

This subtest will check that the defaults to sreport (without AcctAsParent)
and the 'FlatView' switch generates correct reports.

Bug 5793

job_submit programmers guide.

Bug 6178

Bug 6205

This should be fixed in future generations of code to be able to go back
to using libslurm

Bug 6060

Previously the variable was only set for a job step

Move some common logic from gres/gpu and gres/mps into gres/common
Eliminate some redundant string copy/free logic
Remove gres/gpu record combintation logic, which will not work with
  current gres/mps logic
Ignore non-numeric Cores/CPUs configuration parameter
Major updates to test39.18

Bug 6283

# Conflicts:
#	NEWS
#	configure
#	src/common/gres.c
#	src/slurmctld/read_config.c

Bug5793